Generate Plans

Overview

Create implementation plans that another engineer or agent can execute without guessing. Keep plans test-first, incremental, and explicit about paths, commands, and expected outcomes.

Workflow

1. Confirm objective, constraints, and done criteria.
2. Inspect codebase context before planning.
3. Break work into small tasks with clear sequencing.
4. Define verification for every task.
5. Add risks, assumptions, and rollback notes.
6. Save plan to repo_root/agentspace/plans/<inprogress|done|abandoned>/YYYY-MM-DD-<topic>.md.

Planning Rules

• Use concrete file paths, not vague references.
• Keep tasks small enough to complete in 5-20 minutes.
• Require tests before implementation for behavioral changes.
• Include exact commands for build, test, lint, and targeted checks.
• State expected command outcomes when useful.
• Call out dependencies between tasks.
• Prefer minimal design that meets acceptance criteria.

Plan Template

# <Feature> Implementation Plan

**Goal:** <single sentence>
**Scope:** <what is included/excluded>
**Assumptions:** <key assumptions>
**Risks:** <key technical risks>

## Task 1: <name>

**Files:**
- Create: `path/to/new.file`
- Modify: `path/to/existing.file`
- Test: `path/to/test.file`

**Steps:**
1. Add/adjust failing test(s)
2. Run targeted test: `<command>`
3. Implement minimal change
4. Re-run targeted test: `<command>`
5. Run broader checks: `<command>`

**Done When:**
- <observable condition>

## Task 2: <name>
...

## Final Verification
- `<full test/lint/build commands>`

## Rollback Plan
- <how to back out safely if needed>

Output Standard

Plan Lifecycle

Plan state is determined strictly by folder location:

• inprogress/ → Plan currently being executed (default state).
• done/ → Plan fully completed and verified.
• abandoned/ → Plan intentionally stopped or superseded.

Plans must be moved between folders as their lifecycle changes.

• Produce one ordered task list.
• Ensure each task includes files, steps, and done criteria.
• End with final verification and open questions.