draft-card-breakdown

The full skill.

Original instructions from the publisher’s SKILL.md

## Your task: Draft card breakdown

If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following `.agents/docs/card-context.md`.

Workshop how to slice the work into smaller spawned cards and capture the result in the breakdown. On a card, the breakdown lives at `.workhorse/breakdowns/{card-id}/breakdown.md` and the entries become children of this card. On the project surface there is no card: the breakdown lives at `.workhorse/projects/{hash}-{slug}/breakdown.md` and the entries become the project's cards. References to `breakdown.md` below mean whichever of the two applies.

The breakdown is not the implementation plan. The breakdown lists the cards this card splits into; the plan at `.workhorse/plans/{card-id}/plan.md` describes how a single card gets built. You are editing the breakdown here. It has a strict shape:

- An H1 title and an optional intro paragraph
- A flat list of `## ` heading entries, one per spawned card
- Each entry's body is a short description paragraph (and optionally a `<!-- mockups: ... -->` comment) — no checklists, no sub-headings, no nested H3s, no build-step bullets

Once the user is ready, a bulk Create cards action turns each uncreated entry into a real spawned card based on this one. The parent stays as the umbrella while the children carry the implementation work.

### How to run the workshop

1. Read the specs in `specs/`, the card description (on the project surface, the project's PRD), and any existing breakdown at the path above
2. Skim the target repo where it helps you reason about boundaries between the children
3. Talk through how to slice the work — natural seams, dependency order, what each child should own. Ask focused questions one or two at a time
4. As entries become clear, write them into `breakdown.md` as `## ` headings with a short description paragraph beneath. Edit in place as the conversation refines them — adding, splitting, merging, reordering entries is normal
5. If `breakdown.md` does not yet exist, create it at the path above with an H1 title and the entries underneath. Do not create or edit any other file
6. **Suggest mockup carry-forward.** On a card, each entry has an inline Mockups picker for choosing which of the parent's mockups travel with the spawned card. As you write entries, populate the picker by inserting a structured comment line directly under the entry's `## ` heading: `<!-- mockups: slug-one, slug-two -->` (one comment per entry, comma-separated slugs from `.workhorse/design/mockups/{card-id}/`). Pick only the mockups that fit each entry — the user can adjust later
7. Do not trigger bulk-create yourself. The user runs the Create cards action from the editor when they are ready

### What each entry should look like

- The `## ` heading is the spawned card's title — concise, action-oriented, no trailing punctuation, no code suffix (the editor stamps `· CODE` automatically once the card is created)
- The body beneath is the spawned card's description — a short paragraph (or two) covering scope and boundaries. Do not write a checklist, sub-headings, or implementation steps; that detail belongs in each child card's own plan after it is created
- Spawned cards inherit the parent's project and become "based on" the parent via dependencies, so don't restate that

See `specs/card/breakdown.md` for the canonical shape.