Flow Planning

Use this lifecycle skill for PRDs, research, single-flow planning, refinement, revisions, and task creation.

Workflow

1. Read project context, patterns, knowledge chapters, and relevant existing specs before asking questions.
2. Research code paths and external APIs before locking implementation decisions.
3. Create PRDs as roadmap epics and single-flow specs as implementation worksheets.
4. Refine until tasks include concrete files, behavior, tests, commands, and acceptance criteria.
5. Create Beads epics/tasks and sync markdown views according to policy.

Guardrails

• Planning must be decision-complete; do not defer obvious research to implementation.
• Ask only product or tradeoff questions that cannot be answered from the repo.
• Store plans under .agents/specs/<flow_id>/, not ad hoc docs paths.
• Do not modify production code during planning.

Validation

• Confirm every requirement maps to an implementation task and test scenario.
• Confirm tasks are small enough for a low-context executor to complete without guessing.
• Run spec review or code-reviewer validation before presenting final planning artifacts when available.

References Index

• PRD
• Plan
• Research
• Refine
• Revise
• Task

Example

User: "Plan skill trigger optimization."

Action: inspect current skills and validators, ask unresolved product tradeoffs, create a Flow spec with Beads tasks, and refine until the implementation path is explicit.