← docsFull-Lifecycle

/plan-writing

Problem statement → structured task breakdown.

Transforms a problem statement into a structured implementation plan. Breaks work into tasks, identifies dependencies, estimates scope, and defines verification criteria for each task.

Category

Full-Lifecycle

Execution

Problem → task.md with dependencies

Goal

Produce a structured implementation plan with task breakdown, dependencies, and verification criteria.

Scope

Applies to

  • +Any non-trivial feature requiring multiple files or steps

Does not cover

  • −Single-file changes
  • −Tasks that are already well-specified in an issue tracker

Triggers

"Plan this feature""Break down this task""Create implementation plan"Phase 4 of radioactive

Inputs

  • →Feature description or decision log from brainstorming
  • →Tech stack details
  • →Existing codebase structure

Invariants

  • 01Each task must have a file target
  • 02Dependencies must be explicit
  • 03Verification criteria per task

Procedure

  1. Step 1Read decision log / problem statement
  2. Step 2Identify affected files and systems
  3. Step 3Break work into ordered tasks with file targets
  4. Step 4Map dependencies between tasks
  5. Step 5Write verification criteria for each task
  6. Step 6Present plan for user approval (gate)

Outputs

  • ▸task.md with numbered tasks, file targets, dependencies, and verification criteria

Review Gate

  • [ ]Every task has a file target
  • [ ]Dependencies are acyclic and explicit
  • [ ]Verification criteria are testable
  • [ ]User approved the plan