plan_local

Implementation Plan Generator

Input: $ARGUMENTS

Objective

Transform the input into a battle-tested implementation plan through codebase exploration, research, and pattern extraction.

Core Principle: PLAN ONLY - no code written. Create a context-rich document that enables one-pass implementation.

Order: CODEBASE FIRST → REUSE INVENTORY → RESEARCH IF NEEDED → DESIGN → GENERATE.

---

Phase 1: PARSE

Determine Input Type

Input	Action
.prd.md file	Read PRD, extract next pending phase
Other .md file	Read and extract feature description
Free-form text	Use directly as feature input
Blank	Use conversation context

Extract Feature Understanding

• Problem: What are we solving?
• User Story: As a [user], I want to [action], so that [benefit]
• Type: NEW_CAPABILITY / ENHANCEMENT / REFACTOR / BUG_FIX
• Complexity: LOW / MEDIUM / HIGH

Prior Plan Check

If other plans exist in .agents/plans/:

1. Read their summaries to understand what infrastructure they create
2. Note any shared files (e.g., ViewTypeSwitcher.tsx modified by multiple plans)
3. Reference prior plans explicitly: "Depends on: {plan}.plan.md creating {component}"
4. If a shared file will be modified by multiple plans, note the merge order

---

Phase 2: EXPLORE

Study the Codebase

Use the Explore agent to find:

1. Similar implementations - analogous features with file:line references
2. Naming conventions - actual examples from the codebase
3. Error handling patterns - how errors are created and handled
4. Type definitions - relevant interfaces and types
5. Test patterns - test file structure and assertion styles

Document Patterns

Category	File:Lines	Pattern
NAMING	path/to/file.ts:10-15	{pattern description}
ERRORS	path/to/file.ts:20-30	{pattern description}
TYPES	path/to/file.ts:1-10	{pattern description}
TESTS	path/to/test.ts:1-25	{pattern description}