# Plan2Code **A spec-driven workflow for AI coding agents.** banner You work through Plan2Code on a page in your browser. The dashboard lists every step as a card, and each step's questions, progress and sign-offs arrive on that same page while your agent does the work. What you decide still lands in your repo as plain files: an approved plan becomes phase documents, and the agent builds to them one phase at a time, so the next session, the next agent and the next engineer all start from the same specs. One command opens it, every step is a card, and the terminal is always there if you prefer it. Version 3.0.3 Β· MIT Β· πŸ“– [plan2code.jparkerweb.com](https://plan2code.jparkerweb.com) --- ## See it The Plan2Code dashboard for a project mid-build: a Set up card, then the steps in order, with the Implement card marked Suggested and reading Phase 3 of 4 is next. The dashboard, in a project halfway through a build. It suggests the next step for the spec you pick. --- ## Install and start ### Before you start - **Node.js 18 or newer.** Check with `node --version`. No Node? Get it from [nodejs.org](https://nodejs.org/) (the LTS download), or run `winget install OpenJS.NodeJS.LTS` on Windows, `brew install node` on macOS, or use `nvm` on Linux. Then open a new terminal. - **Start from your project.** Open your terminal in the project you want to work on (`cd` into it) before you run anything. Plan2Code works on the folder you start it in. - **Ways in.** `plan2code` (Claude Code, Devin or Codex), or type `/plan2code` in your agent (`$plan2code` in Codex). - **No agent yet?** Install Claude Code, Codex or Devin first, or let the `plan2code` command's setup page walk you through it. Installation needs network access and runs through the [skills CLI](https://skills.sh). To update, run `plan2code update` (or re-run the install command). ```bash npx --allow-git=all git+https://github.com/jparkerweb/plan2code.git ``` This fetches the installer to a temp directory, builds the workflow as Agent Skills, delegates installation to `skills add`, and cleans up after itself. The installed skills work independently from then on. **Back at your prompt with no output at all?** The installer always opens the menu below, so nothing means npm could not reach the repository and hid the reason. Run `git ls-remote https://github.com/jparkerweb/plan2code.git` to see it: usually the network, a proxy or the VPN. The installer opens this menu (cloning and running `node install.js`, below, opens the same one): ``` ╔═════════════════════════════════════════════════════════╗ β•‘ INSTALL PLAN2CODE β•‘ ╠═════════════════════════════════════════════════════════╣ β•‘ I. INSTALL Install skills + the plan2code command β•‘ β•‘ U. UNINSTALL Remove everything Plan2Code installed β•‘ β•‘ A. ADVANCED Project install, dev tools, and more β•‘ β•‘ Q. QUIT Exit β•‘ β•šβ•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β• ``` ### Start 1. `cd` into your project, then run `plan2code`. It starts Claude Code, Devin or Codex on the dashboard, and the dashboard opens in your browser. 2. In a project without an `AGENTS.md`, pick **Set up this project** first: Plan and Quick task need it. 3. Pick a card. Already inside your agent? Type `/plan2code` instead (`$plan2code` in Codex).
About the plan2code command Install (`I`) adds `plan2code` as a global command (Advanced `A` β†’ `D` adds just the command). Run it from any project and the Plan2Code dashboard opens right there, in **Claude Code**, **Devin** or **Codex**. With more than one installed it asks which and remembers your pick; `plan2code --cli claude`, `--cli devin` or `--cli codex` skips the question, and `--model ` chooses the model. It works in cmd, PowerShell, Git Bash, macOS and Linux shells, and needs the Claude Code, Devin or Codex CLI on your `PATH`. After you pick the agent it asks whether to turn its permission prompts off (Yes by default; `--permission-mode bypassPermissions` in Claude Code, `--permission-mode bypass` in Devin, `--dangerously-bypass-approvals-and-sandbox` in Codex, a custom agent's bypass arguments, and no question for a custom agent that has none). `plan2code --keep-permissions` keeps the prompts without asking. The installer then offers a desktop shortcut (answer `y`), which opens a folder picker first. Uninstalling (`U`) removes both.
Using another agent CLI, or none yet Plan2Code runs inside an AI coding agent CLI. With no agent it can run (none of Claude Code, Devin or Codex, and no working custom agent), `plan2code` opens a setup page in your browser (the web console runs it, so no agent is needed). The page lists each agent as **Found**, **Found outside PATH** or **Not found**, with its install commands for your system, a Copy button per command and an **Install page** link. Install one and press **Check again**: no restart needed. An agent found outside `PATH` gets **Use it from here**, which saves where it was found so you never touch `PATH` yourself. Below the list sit four starter templates (GitHub Copilot CLI, OpenCode, Gemini CLI and Pi) for agents Plan2Code does not ship. **Start with this agent** carries the run straight on in the same tab, onto the new agent's dashboard. Naming a built-in that is missing with `--cli ` opens the same page on that agent (a missing custom agent prints its own steps and exits 127). In the desktop app a **Set up an agent** button opens the same page in the window and returns to the launch card with the found agent picked. Where no page can open, such as over SSH or with no display, `plan2code` prints the install commands and install pages and exits with code 127. Once an agent is running, to use a different agent CLI, open the web console's **User Preferences β†’ Agents & models** and add it: a name, the command, and (optionally) its arguments, the start prompt, arguments for skipping permission prompts, and how it takes a model. Custom agents are saved in `~/.plan2code/agents.json` and used by both the `plan2code` command (listed after the built-ins; `--cli ` picks one) and the desktop app's picker. The `/plan2code` start prompt only does something in an agent that loads the installed Plan2Code skills; for any other, leave the start prompt blank and start a skill yourself. Details in [.readme/web-console.md](.readme/web-console.md#agents--models).
About the desktop app The installer also offers the **Plan2Code desktop app**: one window with the dashboard and your agent's terminal side by side, docked right (or bottom) and collapsible. Every console page, not only the dashboard, opens inside it. A launch card asks which agent, model and effort to start on, with permission checks off as its own tick (on by default, matching the terminal flow; untick it to keep the agent's approval prompts). A **New Session** button in the top bar replaces the agent with a fresh one on a brief built from the session, and the console's own Session meter points at it when a session is getting long. Once it is installed, `plan2code` opens the app instead of running the agent in your terminal. `plan2code --classic` keeps the terminal flow, and so does a Linux machine with no display (over SSH, say) or any machine over an SSH session. `plan2code update` updates the skills, the command and the app together, and the bar offers the same **Update skills** when the app and the installed skills disagree. The app can also build a whole spec unattended with the Implementation Loop; see [docs/desktop-app.md](docs/desktop-app.md#implementation-loop). The first release is unsigned, so macOS (**Open Anyway** in System Settings, Privacy & Security) or Windows (**More info**, then **Run anyway**) may ask you to allow it once. The app starts the agent with its normal approval prompts unless you tick the launch card's permission-checks-off option (the plain `plan2code` command above, without the app, asks instead, with prompts off by default too). Details: [docs/desktop-app.md](docs/desktop-app.md).
**Supported tools:** every agent supported by the skills CLI, including Claude Code Β· Cursor Β· GitHub Copilot Β· Windsurf Β· Codex Β· Continue Β· Codeium Β· Zed Β· Amp Β· OpenCode Β· Devin Β· Crush Β· Pi Β· Gemini CLI Β· Cline Β· Roo Β· Kilo Β· Goose Β· Trae Β· Qwen Code. The installer keeps one canonical copy of each skill under `~/.agents/skills/` and links it into agents that maintain their own directory. To update, run `plan2code update` (or re-run the install command). Use the installer rather than calling `skills add` against the repository root: recursive discovery would also find maintainer-only skills under `.claude/skills/`. The installer targets `skills/` explicitly.
Prefer to clone? ```bash git clone https://github.com/jparkerweb/plan2code.git cd plan2code node install.js # Only if you plan to modify or contribute to Plan2Code itself npm install && npx husky ```
--- ## A session on the page **Answer the questions.** They arrive a few at a time, each option with its trade-off written beside it, and a progress bar says how far along you are. A Plan question card, How tasks are paged, with three options, the first marked Suggested, each with its trade-off underneath. **Watch the build.** Tasks tick off as they land, and the line beside Planny says what is being worked on right now. A phase of a task API being built: 5 of 11 done on the progress bar, and the phase's task list with the first five ticked. **Sign off.** Read the completion report, then approve the phase or ask for changes. In Implement, you can also have the code reviewed first; Implement + review has already done it. The Approve this phase card, with a button to read the completion report and three choices: Review the code first, Approve this phase, and I want changes. **Ask a quick question any time.** The Ask tab is a chat beside the cards, answered at the agent's next check-in, and it never holds up your answers. The Ask tab: the question Where are tasks paged? and Plan2Code's answer naming the file. There is more on the page when you need it. Notes on any question can carry screenshots and documents. The folder label in the bottom bar opens your workspace, where you add other folders as read-only context and point at them by `@name`. The **Notebook** in the top bar is a private pad of your own for the folder, in Markdown with pictures, that the agent reads only when you start a workflow from one of its tabs on the dashboard and send the box it fills. The **die** beside it opens **Activities**, two small games (Snake and Mini golf) to play through a long wait, which pause the moment it is your turn. The session meter in the top bar turns from green to red as a session grows long and suggests a fresh one. **Stop session** saves your place and gives you the command to carry on later, and **Back to the dashboard** takes you home to pick the next step in the same session. --- ## The workflow ``` β”Œβ•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β” β•Ž0 PATHFINDERβ•Ž optional Β· for an idea too big or unclear to plan β””β•΄β•΄β•΄β•΄β•΄β•΄β”¬β•΄β•΄β•΄β•΄β•΄β”˜ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ 1 PLAN │─>β”‚ 2 DOCUMENT │─>β”‚3 IMPLEMENT │─>β•Ž REVIEW β•Žβ”€>β”‚ 4 FINALIZE β”‚ β”‚decide what β”‚ β”‚ draw it as β”‚ β”‚build to theβ”‚ β•Ž optional β•Ž β”‚verify, sum,β”‚ β”‚ to build β”‚ β”‚phase specs β”‚ β”‚ drawing β”‚ β•Ž any time β•Ž β”‚ archive β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β•΄β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ short sessions: fresh when the meter turns red, and before a big step β”œβ—€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ one feature, start to archive ──────────────────▢─ ``` Each box is a card on the dashboard. Chaining a couple of small steps in one session is fine, but start a fresh session before a big plan or build step: planning context leaking into implementation is where most agent drift starts. The dashboard's cards, and when each one lights up for the spec you pick: | Card | What it is for | Lights up when | |------|----------------|----------------| | Set up this project | Reads your project and writes AGENTS.md, the guide every later step works from. | The project has no AGENTS.md yet | | Refresh AGENTS.md | Brings AGENTS.md and its notes up to date with what the project has learned lately. | The project has an AGENTS.md | | Pathfinder | A foggy idea becomes a clear list of decisions, settled one question at a time. | You start fresh, or the spec is still being explored | | Plan | Requirements, technical design and your approval: the shape of what gets built. | You start fresh, or the spec has a finished Pathfinder map, a drafted plan or a bug diagnosis | | Revise the plan | Requirements changed mid-build? Adjust the plan without starting over. | The spec is written up into phases, built or not | | Document | The plan becomes a checklist of small tasks, grouped into phases, that a developer can just do. | The spec has a drafted plan | | Implement | Builds the next phase, task by task, with a report and your sign-off at the end. | The spec has phases with tasks still to build | | Implement + review | One phase built, then a careful review of the changes, then your sign-off. All in one run. | The spec has phases with tasks still to build | | Finalize | Checks the work, writes the summary, files the specs away and suggests the commit message. | Every task in the spec is done | | Quick task | Too small for the full process? A quick plan, then it just builds it. | Always (suggested when the spec is a diagnosed bug) | | Review | A second opinion on the changes. Problems ranked, and you pick what gets fixed. | Always | | Handoff | Pack this conversation into a document a fresh session can pick up cold. Any skill's **Stop with a handoff** writes one too, and the dashboard lists them to pick up. | Always | | Codebase X-ray | Explain how and why an area works, or find the rough spots worth fixing. | Always | | Diagnose a bug | Find a bug's cause and write it up, without fixing it. | Always | | Get a PR ready | Runs the checks your branch needs, says if it is ready, and writes the PR description to copy. Never commits, pushes or opens the PR. | Always | | Write missing tests | Finds code with no tests and writes unit and integration tests in your project's own style. Never changes source code. | Always | | Changelog | Checks the CHANGELOG version against the main branch and suggests entries for what is new. | Always | | Git | Branches, pull, push and commits on one board, asking before anything leaves your machine. | Always (offers to start a repository outside one) | --- ## The four rules that do most of the work **1 Β· Keep each session short.** Chaining a couple of small skills on the dashboard is fine. Start a fresh console session when the session meter turns red, and always before a big planning or build step. The specs on disk carry everything between sessions. **2 Β· No code until the plan hits 90% confidence.** Step 1 will not finalize below the threshold. Under it, the agent keeps asking and keeps reading your code β€” and writes every assumption down where you can argue with it. **3 Β· Checkboxes are the state, not the chat.** Progress lives in the spec files. Any agent, any session, resumes cold from them. **4 Β· Approve a phase to close it.** On the sign-off card, or by replying `approved` in the terminal. Nothing advances on a guess about what you meant. --- ## What lands in your repo Each feature gets a folder under `specs/` (the plan, the overview and one file per phase), and Step 4 moves it to `specs--completed/`. The layout and progress marks are on the [quick reference](QUICK-REFERENCE.md#file-structure). Add `specs/` to your project's `.gitignore`: it's your working drawing, not a deliverable. Share a folder deliberately with `git add -f` when you want to. Step 2 marks which phases don't share files. Open a second agent on one of those, and the `[/]` marks keep the two out of each other's way. --- ## The six steps in detail Each step is its own run, and the specs on disk are the only thing carried from one to the next. Chain a small one onto the last, or start a fresh session for a big one (rule 1). ### 0 Β· Pathfinder 🧭 (optional) On the page: one question at a time with the options and their trade-offs, the map growing in its own tab, and a **Write a brief** button for a printable summary. Some ideas are too big and unclear to plan: you can feel the shape of the work but you can't write it as requirements, so planning would just invent the answers. Pathfinder finds the *way* to the destination; Step 1 then walks it. 1. **Name the destination** β€” one or two lines fixing what this effort is finding its way to. Settled first, because it fixes scope. It also asks where the map should live: **local files** under gitignored `specs/` (private, solo β€” the default), or **GitHub Issues** (a map issue with one sub-issue per decision, native blocking, so your team can see and work the frontier in the tracker). 2. **Chart the map** β€” a breadth-first grilling surfaces the open decisions. Anything you can phrase *sharply* becomes a question file; anything you can only sense stays listed as fog. 3. **Clear the questions one at a time** β€” resolving one burns off the fog behind it, graduating whatever just became sharp into new questions. After each decision it offers a menu: take the next question here, or start fresh β€” recommended after about three, to keep the agent sharp. Ask for a **brief** at any point and you get a dated, plain-English summary of what has been decided, what is still open, and what is next β€” meeting minutes, with no jargon in them. 4. **Hand off** β€” when nothing is left to decide, it writes a `PLAN-DRAFT` that `/plan2code-1-plan` resumes from at Phase 4, with requirements, context, and scope already answered. **Question types:** `grill` (a decision only you can make β€” the default) Β· `research` (a fact gates it; background agents resolve these, several in parallel) Β· `sketch` (you need something concrete to react to) Β· `legwork` (manual work that has to happen before a decision is possible). It never answers its own questions, and it **plans, it never builds.** When the urge to just build it arrives, the map is done. Skip Step 0 entirely when you already know what you're building. **Out:** `specs//pathfinder/map.md` + `questions/` (or a `pathfinder:map` issue and its sub-issues) β†’ `PLAN-DRAFT-.md`. The draft is always a local file β€” that is what Step 1 reads. ### 1 Β· Plan πŸ€” On the page: questions in batches of up to three, the phase breakdown as a list you can reorder and edit, and a sign-off at each stage. The agent works as a senior architect through seven phases, stopping for you after each: requirements analysis Β· system context (reading your actual codebase) Β· scope assessment (a large project saves and resumes in a fresh session) Β· tech stack (needs your explicit sign-off) Β· architecture design Β· technical specification Β· transition decision. It won't finalize below **90% confidence**, and every assumption it makes is written into the draft. **In:** a description of the feature. **Out:** `PLAN-DRAFT-.md` + `PLAN-CONVERSATION-.md` ### 2 Β· Document πŸ“ On the page: a question only where the plan leaves something open, each phase file appearing as its own tab as it is written, and one sign-off at the end. The plan becomes the drawing. One `overview.md` with the phase checklist, plus one file per phase of one-story-point tasks. Each phase is **self-contained** β€” an agent opening `phase-3.md` cold needs nothing else to build it. Unit and E2E tests are excluded unless you ask for them. The overview also identifies the **parallel execution groups**: phases with no shared files or dependencies, safe to run in separate agents at once. **In:** the `PLAN-DRAFT`. **Out:** `overview.md` + `phase-1…N.md` ### 3 Β· Implement ⚑ On the page: a progress bar and the phase's task list ticking over as tasks land, then the completion report and a sign-off card where you approve, ask for changes, or have the code reviewed first. Point it at `overview.md` and it does the rest: finds the next unchecked phase, implements every task exactly as specified, ticks tasks off as they land, then reviews its own work against the spec and writes a completion summary. One phase per conversation. It won't run tests unless the phase says to. **In:** `specs//overview.md`. **Out:** working code, and updated checkboxes. Want a second pair of eyes before you sign off? `/plan2code-3-implement-review` builds the phase the same way, runs a focused review and the fixes you pick, and only then asks for approval. ### Review πŸ”¬ β€” optional, any time On the page: a few questions on scope, the findings as a report you can read in full, and a list where you tick what gets fixed. An independent second opinion, not a rubber stamp. It figures out its own scope (conversation context, your instruction, or the git diff as a fallback), analyses across 11 dimensions, and ranks findings Critical / Warning / Suggestion. Every finding cites a file and a line, or it gets dropped β€” and the review pass is read-only. It fixes things only if you ask, and verifies each fix afterwards. Spec-aware when `specs/` exists, and works fine without it. Most useful right after a planning or implementation step, but there's no wrong time to run it. ### 4 Β· Finalize 🧹 On the page: the task audit and the summary as reports, a list of the doc updates to approve, and a confirmation before anything is archived. Validates every task against its phase spec, writes the summary and the list of files touched, flags the docs that drifted (`README`, `CHANGELOG`, `AGENTS.md`), then archives the whole spec folder β€” `pathfinder/` included β€” to `specs--completed/`. That folder is the record of *why* the code looks like this. **In:** `specs//overview.md`. **Out:** archived specs. --- ## Prefer the terminal? Every skill also runs right in the terminal. Each one asks at the start whether you want the web console or the terminal; add `--web` to skip the question and go straight to the web console: `/plan2code-1-plan --web plan a REST API for tasks`. | Command | Use it when | |---------|-------------| | `/plan2code` | Open the dashboard in the web console: every skill below as a card, launched on the page | | `/plan2code-0-pathfinder` | The idea is too big and unclear to plan. Charts it as decisions, clears them one at a time, hands a hot plan draft to Step 1 | | `/plan2code-1-plan` | Starting a feature. Full requirements β†’ architecture pass | | `/plan2code-2-document` | Planning is done. Turn the plan into phase specs | | `/plan2code-3-implement` | Build the next phase (one per conversation) | | `/plan2code-3-implement-review` | Build the next phase and review it before you approve it (instead of `/plan2code-3-implement`) | | `/plan2code-review` | Independent second opinion on local changes, then optional fixes | | `/plan2code-4-finalize` | All phases done. Validate, summarize, archive | | `/plan2code-init` | Generate this repo's `AGENTS.md` so every agent starts informed | | `/plan2code-init-update` | Fold what you learned this session back into `AGENTS.md` | | `/plan2code-quick-task` | A small change that doesn't warrant the full sequence | | `/plan2code-1b-revise-plan` | Requirements moved mid-build. Revise the specs, not the code | | `/plan2code-handoff` | Compact this conversation into a doc the next one resumes from, saved in `~/.plan2code/handoffs/` and listed on the dashboard to pick up | | `/plan2code-xray` | Explain how and why an area of the code works (citing files, commits and PRs), or rank the rough spots worth fixing into a brief for Pathfinder or Plan; never edits code | | `/plan2code-diagnose` | Find a bug's cause and write it up as `specs//DIAGNOSIS-.md` without fixing it, then offer `/plan2code-quick-task` to fix it, or `/plan2code-1-plan` when the fix is big | | `/plan2code-pr-prep` | Before you open a pull request. Picks the checks the branch's changes need from the project's `## Test map` (or its config files), runs the ones you keep, says Ready, Ready with notes or Not ready, and writes a PR description to copy with the create-a-PR link; never commits, pushes or opens the PR | | `/plan2code-test` | Parts of the code have no tests. Asks where to look, finds the untested files (plus real coverage when the project already has a coverage tool), shows a plan in the project's own style, then writes and runs unit and integration tests; never changes source code, hands a real bug to `/plan2code-diagnose` | | `/plan2code-changelog` | Check the CHANGELOG version against the default branch, suggest entries for new work you can edit, keep `package.json` aligned, then hand off to Git to commit | | `/plan2code-git` | Branches, pull, push and commits on one board (or plain instructions in the terminal); asks before every push, publish and delete | --- ## Troubleshooting **The skills aren't recognized.** Re-run the installer and restart your AI tool. Confirm the global install with `npx skills list -g`. For a project install, check the generated directories aren't gitignored. **Your tool doesn't read Agent Skills.** Since v2.2.0, Plan2Code ships only as skills. If your tool has no skill support, paste the relevant `src/plan2code-*.md` manually or point it at the installed copy under `~/.agents/skills/`. **The agent starts coding during planning.** The prompts forbid it, but models drift. Say: "Stay in planning mode. Do not write code yet." **The agent doesn't know what to implement.** Give it the path to `overview.md` β€” it reads the phase file itself from there. **You lost track between sessions.** `overview.md` has the phase status; the phase files have the task status. That's the whole state. **The agent isn't following the spec.** Point at the specific phase document and tell it to re-read the requirements. **Too many or too few phases.** Fix it in Step 2 β€” a phase should be a logical grouping of work, not a fixed size. **The agent runs on another machine, or over SSH.** The page is served on `127.0.0.1` of the machine the agent runs on, so your browser can only reach it there. A forwarded port often works; otherwise work in the terminal, which loses nothing. **Web console problems** (lost contact, a closed tab, a dead link): see [.readme/web-console.md](.readme/web-console.md#troubleshooting). --- ## Customizing The prompts are yours to edit. Common changes: add testing requirements in Step 2, move the 90% confidence threshold in Step 1, restructure the `specs/` layout, or add review gates to Step 3. Source files live in `src/`; run `npm run build:skills`, then re-run `node install.js` to push your edits out through the skills CLI. --- ## Dive deeper Core reference: - **[.readme/web-console.md](.readme/web-console.md)**: the full guide to the web console, from the dashboard to the last sign-off, including the private Notebook and Activities in the top bar - **[QUICK-REFERENCE.md](QUICK-REFERENCE.md)** β€” the one-page card: commands, inputs, outputs, decision tree - **[.readme/walkthrough.md](.readme/walkthrough.md)** β€” one feature from a sentence to archived specs, session by session - **[AGENTS.md](AGENTS.md)** β€” architecture and contributor guide for this repo - **[CHANGELOG.md](CHANGELOG.md)** β€” what changed, and why Optional tooling β€” none of it is required to use the workflow: - **[.readme/status-line.md](.readme/status-line.md)** β€” three-line Claude Code status bar: model, context, quota, diff - **[.readme/metrics.md](.readme/metrics.md)** β€” `plan2code-metrics`, measuring and improving the prompts themselves - **[.readme/test-bot.md](.readme/test-bot.md)** β€” `plan2code-bot`, maintainer harness that runs the whole workflow unattended