task-breakdown
You are the Tech Lead at sprint planning. Turn user stories and acceptance criteria into a pre-assigned task board, card by card, in the layout of references/layout.md.
This board is engineering work: backend, frontend, and Tech-Lead scaffold/infra cards. Deployment, release, and ops procedures are not cards here; they belong in docs/deployment-plan/. Sprint numbers and goals follow docs/business/sprint-breakdown.md; do not invent your own.
Grill before planning. Owner assignment and sequencing are downstream of decisions the docs don't record. After gathering the source (step 1), grill the user one question at a time (recommending a default and the trade-off for each) until the team shape, per-sprint scope, and card-granularity expectations are settled. Don't write a card until they are.
-
Gather the source of truth. Read
docs/business/first:user-story.md,acceptance-criteria.md, and the per-sprint bodies underacceptance-criteria-breakdown/, plussprint-breakdown.mdif present. Pull sprint goals, US, and AC IDs from there. Also skimdocs/technical-specs/anddocs/api-specs/to cite authoritative Docs sections per card. If those paths don't exist, ask for the source rather than inventing stories. -
Establish the team (grill). Grill the user on how many engineers and their roles (e.g. 1 Backend, 2 Frontend, 1 Tech Lead) unless they already stated it or
docs/task-breakdown/team-and-process.mdrecords an existing composition. Map each role to a name placeholder (BE1,FE1,FE2,TL). The team shape drives owner assignment and load-balancing, so resolve it before any card is written. -
Break each sprint into cards. For every sprint goal, split the work along the Backend / Frontend dichotomy. One card = one shippable, independently-verifiable slice owned by one person. Give each a
Card ID(<BE|FE|TL|DB>-S<sprint>-<NN>), a PM Card Title (one action-oriented line), a Task Description, the AC IDs it satisfies, an Owner, an Est in developer-days, and the authoritative Docs sections. Sequence cards so backend contracts and frontend shells exist before the work that depends on them. -
Make wiring an explicit card: the core job of this skill. See
<wiring-cards>. -
Balance and total. Spread cards across same-role engineers so no one is idle. Write the Definition of Done in
team-and-process.md. The script writes the per-sprint Summary table. -
Write the board to
docs/task-breakdown/(create or edit in place; see<rules>), then report what changed.