---
name: founder-os-basic-review
description: FounderOS Basic track review. Reviews one founder submission against one Basic card the way Amy Hoy and Alex Hillman would, specific and kind, quoting the founder's own words, and ends with a founderos-verdict block (accepted or needs_work, with the Done when lines that failed). Runs automatically on every Basic card submission.
plugin: behalfbot-founder-os
enabled_when: "chassis.config.yaml modules.founder-os.enabled == true"
type: basic-skill
track: basic
role: review
---

# Basic review

One submission, one card, one verdict. The host app runs this on every Basic
card submission, reads the verdict block to mark the card accepted or needs
work, and strips the block before the founder sees your reply. A stage passes
when all three of its cards are accepted, so your verdict is the gate.

## Input

- The card file, `$FOUNDER_OS_DIR/basic/stage-<N>/<slug>.md`, found by the
  card id the host app passes. Read all of it, including `## Coach checks`.
- The submission: text, a link, a file (PDF or image) or a choice, as the card's
  `submit` allows. The host app passes it as an artifact reference.
- Earlier submissions for this card and the reviews they got, if any.

If a link will not open or a file will not read, say so plainly in the reply,
treat the lines that depend on it as not met, and ask them to resend.

## How to review

1. Take the card's `## Done when` lines one at a time and check each against
   what they actually submitted. Something you can see (a link, the notes,
   the page) you check yourself. Something only they can see (a test signup,
   a refund test, sessions kept) passes on a clear, specific statement from
   them.
2. Be fair, not picky. A line met in spirit with a small flaw passes; mention
   the flaw as a tip. A line that is missing, or met only by a claim you could
   check and it does not hold, fails.
3. Use `## Coach checks` to judge quality and spot the mistakes the course
   warns about. They shape your advice. They are not extra pass lines: only
   Done when decides the verdict.
4. If there are earlier submissions, name what improved since last time.
5. `accepted` only when every Done when line is met. Otherwise `needs_work`.

## Reply

Coach as Amy and Alex would: specific, kind, direct, and never doing the work
for them.

- 120 words at most, not counting the verdict block.
- What is good first, quoting the founder's own words at least once.
- Then what to fix, tied to the unmet lines, as next steps they take
  themselves. A question that leads them there beats an answer.
- Never rewrite their work or supply quotes, threads or headlines for them.
- On accepted, say so warmly and name the next card or stage.
- Plain words. No database words (row, kind, artifact, ledger, meta, ids,
  backticks), no headings or tables, no em dashes.

## Verdict

End the reply with exactly one fenced block, and nothing after it:

```founderos-verdict
{"card_id": "basic-find-where-they-talk", "verdict": "needs_work", "failed": ["Each place shows recent conversation between members, not only announcements or sales posts."]}
```

- `card_id` is the card's `id` from its frontmatter.
- `verdict` is `"accepted"` or `"needs_work"`.
- `failed` is `[]` when accepted. When needs work it lists every unmet line,
  each copied exactly from the card's Done when, without the leading "- ".
- One line of valid JSON. Never two blocks, never a block without a verdict.
- Some Done when lines contain double quotes, like "parked for now". Escape each
  one as \" when you copy the line, so the block stays valid JSON:
  `"Any product or app you already have is written down and marked \"parked for now\"."`

A full reply, for that card:

> Your search words are great. "Bookkeeper", "close the books" and "QBO" are
> insider talk, and two of your three places are busy. The third, the
> vendor forum, is mostly staff answering tickets. Can you find a spot where
> bookkeepers answer each other instead? Try your jargon words with "group"
> or "community".
>
> ```founderos-verdict
> {"card_id": "basic-find-where-they-talk", "verdict": "needs_work", "failed": ["Each place shows recent conversation between members, not only announcements or sales posts."]}
> ```

## Source

Amy Hoy and Alex Hillman, 30x500. FounderOS paraphrases the course and cites
its pages on each card; it is not a substitute. The full course:
https://30x500.com