workflows-plan

Create an implementation plan for: $ARGUMENTS

Purpose

You are executing Stage 3 (Planning) of the development workflow. The spec with frontmatter claims exists from Stage 2. Your job is to decompose the work into sub-agent-sized tasks, identify dependencies, and produce a plan file that Stage 4 can execute.

Pre-Conditions

Before starting, verify:

1. .workflow/state.json exists and currentStage is "planning"
2. A spec exists (check stages.dev-docs.artifacts.spec in state)
3. Spec frontmatter includes at least one claim (check stages.dev-docs.artifacts.spec in state)

If pre-conditions are not met, report what's missing and halt.

Process

Step 1: Gather Context

Read the spec (frontmatter + body) from Stage 2, then investigate the codebase:

1. Read the spec: Understand what needs to be built
2. Read spec claims: Understand falsifiable claims and required evidence
3. Map the affected code: Use Glob/Grep to find files that will need changes
4. Check for prior learnings: Search agent memory and compound learnings for relevant patterns
5. Check existing tests: Identify test files that will need updates

Step 2: Decompose into Tasks

Break the implementation into discrete, sub-agent-sized units of work. Each task must be:

• Atomic: One task = one logical change = one commit
• Testable: Each task has clear acceptance criteria
• Ordered: Dependencies between tasks are explicit

For each task, define:

### Task N: <title>

**Files**: [list of files to create/modify]
**Depends on**: [task numbers, or "none"]
**Acceptance criteria**:
- [ ] [specific, verifiable condition]
- [ ] [specific, verifiable condition]

**Notes**: [implementation hints, gotchas from codebase investigation]

Step 3: Identify Risks

For each task, flag:

• Files with high churn or complexity
• Areas where the spec's assumptions may not hold
• External dependencies or integration points
• Tests that may need significant rework