ITECHDEV-MX When to Use
Position 2 of a story-creation chain after plan-ceo-review returned
verdict NOW. Skip when the verdict was LATER or NEVER — that
chain ends at position 1.
Rules
- Read both prior artifacts before producing the plan. The
reframe (
0-) gives the WHAT; the CEO plan (1-) gives priority and constraints. - Decompose the work into 3-7 concrete tasks. Each task has: one-sentence description, affected packages/files, estimated effort (S/M/L), risk level.
- Map skills + recipes that apply to each task. Use
aria_get_skillsto discover. Do not invent skill names. - Identify migrations if any DB schema changes are implied. Flag them prominently — they cost real time.
- Identify required tests by category (unit, integration, E2E). Avoid "add tests" as a single line item — be specific.
- Sections:
## Task breakdown,## Skills + recipes that apply,## Migrations,## Tests required,## Risks,## Definition of Done. - Word count target: 500–1500.
Verification
- Both prior artifacts referenced explicitly
- Task breakdown has 3-7 items
- Each task lists effort + risk
- At least one skill/recipe mapped per non-trivial task
- Migrations explicitly addressed (even if "none")
- DoD checklist is testable
- Artifact at
/Historias/<slug>/2-eng-plan.md