Capture Context

Make the plan file self-contained so implementation can proceed after clearing context.

Step 1: Locate the Plan File

Find the active plan file path from the plan mode system prompt. Read the file to determine whether it already has content.

If no plan file exists, create one at the path specified by plan mode.

Step 2: Scan the Conversation

Extract information across these categories. Skip any category where nothing relevant was discussed.

1. Work State — Commits made, branches created, PRs opened. Current branch and its relationship to the base branch. Build and test status. What is implemented vs. what remains.
2. Codebase Findings — Files explored and their relevance. Reference implementations discovered (exact file paths and line ranges). Patterns and utilities identified for reuse. Architecture or module boundaries understood.
3. Decisions and Rationale — Approaches chosen and why. Alternatives considered and why they were rejected. Constraints that shaped the design. User preferences expressed during discussion.
4. Requirements Refinement — How the original request evolved through discussion. Scope narrowed or expanded. Acceptance criteria clarified. Dependencies identified.
5. Open Questions — Unresolved items that need attention during implementation. Assumptions made that should be verified. Risks or unknowns flagged.