<title>Plan2Code: plan and build with your AI agent in your browser</title>
<metaname="description"content="Plan and build with an AI coding agent on a page in your browser. You answer the questions and approve each phase, and the specs land in your repo as plain files.">
<h1id="hero-title">Plan and build with your AI agent, on one page.</h1>
<pclass="lede">Plan2Code asks the questions, drafts the plan and builds it one phase at a time. You answer and approve in your browser, and the specs land in your repo.</p>
<li><strong>Node.js 18 or newer.</strong> Check with <code>node --version</code>. No Node? Get it from <ahref="https://nodejs.org/">nodejs.org</a> (the LTS download), or run <code>winget install OpenJS.NodeJS.LTS</code> on Windows, <code>brew install node</code> on macOS, or use <code>nvm</code> on Linux. Then open a new terminal.</li>
<li><strong>Start from your project.</strong> Open your terminal in the project you want to work on (<code>cd</code> into it) before you run anything. Plan2Code works on the folder you start it in.</li>
<li><strong>Ways in.</strong><code>plan2code</code> (Claude Code, Devin or Codex), or type <code>/plan2code</code> in your agent (<code>$plan2code</code> in Codex).</li>
<pclass="then">then, from your project, run <code>plan2code</code> (Claude Code, Devin or Codex), or type <code>/plan2code</code> in your agent (<code>$plan2code</code> in Codex).</p>
<pclass="then">It always opens a menu; no output at all means npm could not reach the repository and hid the reason: <code>git ls-remote https://github.com/jparkerweb/plan2code.git</code> shows why.</p>
<imgsrc="screenshots/dashboard-light.webp"width="2560"height="1600"alt="The Plan2Code dashboard for a task API that is half built: a Set up card, then the steps in order, with the Implement card marked Suggested and reading Phase 3 of 4 is next.">
<imgsrc="screenshots/question-light.webp"width="2560"height="1600"loading="lazy"alt="A Plan question card, How tasks are paged, with three options, the first marked Suggested, each with its trade-off underneath.">
</picture>
<div>
<spanclass="k"aria-hidden="true">1</span>
<h3>Pick a card, answer on the page</h3>
<p>Pick a step on the dashboard and it starts right there. Questions arrive a few at a time, each option with its trade-off written under it.</p>
<imgsrc="screenshots/build-light.webp"width="2560"height="1600"loading="lazy"alt="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.">
</picture>
<div>
<spanclass="k"aria-hidden="true">2</span>
<h3>Watch it build</h3>
<p>Tasks tick off as they land, and the line beside Planny says what is being worked on right now.</p>
<imgsrc="screenshots/signoff-light.webp"width="2560"height="1600"loading="lazy"alt="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.">
</picture>
<div>
<spanclass="k"aria-hidden="true">3</span>
<h3>Sign off</h3>
<p>Read the completion report, then approve the phase or ask for changes. In Implement, you can also have the code reviewed first.</p>
<pclass="intro muted">Every step is a card on the dashboard. Each one writes files the next one reads, so any session can pick up cold.</p>
<olclass="line">
<liclass="opt"><h3>Pathfinder</h3><spanclass="chip">Step 0 · optional</span><p>A foggy idea becomes a clear list of decisions, settled one question at a time. <code>/plan2code-0-pathfinder</code></p></li>
<li><h3>Plan</h3><spanclass="chip">Step 1</span><p>Requirements, technical design and your approval: the shape of what gets built. <code>/plan2code-1-plan</code></p></li>
<li><h3>Document</h3><spanclass="chip">Step 2</span><p>The plan becomes a checklist of small tasks, grouped into phases, that a developer can just do. <code>/plan2code-2-document</code></p></li>
<li><h3>Implement</h3><spanclass="chip">Step 3 · once per phase</span><p>Builds the next phase, task by task, with a report and your sign-off at the end. <strong>Implement + review</strong> adds a careful review of the changes before the sign-off. <code>/plan2code-3-implement</code></p></li>
<li><h3>Finalize</h3><spanclass="chip">Step 4</span><p>Checks the work, writes the summary, files the specs away and suggests the commit message. <code>/plan2code-4-finalize</code></p></li>
</ol>
<divclass="utils">
<divclass="util"><spanclass="chip">Any time</span><h3>Quick task</h3><p>Too small for the full process? A quick plan, then it just builds it.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Review</h3><p>A second opinion on the changes. Problems ranked, and you pick what gets fixed.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Handoff</h3><p>Pack the current session into a document a fresh session can pick up cold.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Codebase X-ray</h3><p>Explains how and why an area works, or ranks the rough spots worth fixing into a brief for planning.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Diagnose a bug</h3><p>Finds a bug's cause and writes it up without fixing it, then hands the fix to Quick task, or to Plan when it is big.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Changelog</h3><p>Picks the next version and drafts the entries, which you edit before Git commits them.</p></div>
<divclass="util"><spanclass="chip">Any time</span><h3>Git</h3><p>A board for branches, pull, push and commits that opens on the likely next step.</p></div>
<imgsrc="screenshots/git-light.webp"width="2560"height="1600"loading="lazy"alt="The git board on feature/task-endpoints: the Changes tab, badged 3, opens on a Next step card reading Commit 3 files, above the three changed files ticked for the commit. Branches and Sync tabs and a Done with git button sit beside it.">
</picture>
<div>
<h3>The git board</h3>
<p>Three tabs, <strong>Changes</strong>, <strong>Branches</strong> and <strong>Sync</strong>, and it opens on the one holding your likely next step: commit, pull, push, publish, open a pull request or tidy up branches. That step is one main button. Each tab badges what is waiting on it, a stopped rebase or merge gets one block with every file marked, and nothing is pushed, published or deleted without asking. It never force-pushes.</p>
<h2id="features-title">What the page gives you</h2>
<pclass="intro muted">The same workflow as the terminal, with more room to think.</p>
<divclass="feat">
<div><h3>Trade-offs in plain view</h3><p>Questions arrive a few at a time, each option with its trade-off written under it, so you choose rather than guess.</p></div>
<div><h3>Review before you approve</h3><p>Review the code first, on the sign-off card, reviews exactly the files the phase changed. You tick which findings get fixed, then approve.</p></div>
<div><h3>The Ask tab</h3><p>A chat beside the cards for anything you want to know. It is answered at the agent's next check-in and never holds up your answers.</p></div>
<div><h3>Attachments on notes</h3><p>Paste a screenshot or attach a document to a note on any question, and show instead of describe.</p></div>
<div><h3>A notebook of your own</h3><p>A private pad for each project folder, in Markdown with pictures. It never goes into your project, and the agent never sees it.</p></div>
<div><h3>Workspace folders</h3><p>Add a shared library or a design folder as read-only context, and point at it by its <code>@name</code>.</p></div>
<div><h3>Session meter</h3><p>A ring in the top bar turns from green to red as a session grows long, and suggests when a fresh one would serve you better.</p></div>
<div><h3>Runs on your machine</h3><p>A small program Plan2Code starts for you serves the page on <code>127.0.0.1</code>. No account, no dependencies, and nothing leaves your computer.</p></div>
<imgsrc="screenshots/ask-light.webp"width="2560"height="1600"loading="lazy"alt="The Ask tab: the question Where are tasks paged? and Plan2Code's answer naming the file.">
</picture>
<figcaption>The Ask tab, answered between tasks.</figcaption>
<imgsrc="screenshots/finish-light.webp"width="2560"height="1600"loading="lazy"alt="The finished screen after a phase: what happened, the next command with a Copy button, and a Back to the dashboard button.">
</picture>
<figcaption>Every ending says what to run next.</figcaption>
<imgsrc="screenshots/notepad-light.webp"width="2560"height="1600"loading="lazy"alt="The Notebook open over a question: two named tabs, and a heading, bullets and bold styled in place as they are typed.">
<pclass="intro muted">Four rules do most of the work.</p>
<olclass="rules">
<li><div><h3>Keep each session short.</h3><p>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.</p></div></li>
<li><div><h3>No code until the plan hits 90% confidence.</h3><p>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.</p></div></li>
<li><div><h3>Checkboxes are the state, not the chat.</h3><p>Progress lives in the spec files. Any agent, any session, resumes cold from them.</p></div></li>
<li><div><h3>Approve a phase to close it.</h3><p>On the sign-off card, or by replying <code>approved</code> in the terminal. Nothing advances on a guess about what you meant.</p></div></li>
<pclass="muted">Every skill also runs right in the terminal. Each one asks at the start whether you want the page or the terminal; add <code>--web</code> to skip the question and go straight to the page.</p>
<p><ahref="https://github.com/jparkerweb/plan2code#prefer-the-terminal">See every command in the README</a></p>
</div>
<preclass="term">/plan2code
/plan2code-1-plan --web plan a REST API for tasks</pre>
</div>
</section>
<sectionclass="s alt close"id="install"aria-labelledby="install-title">
<pclass="muted">Run it again any time to update.</p>
<divclass="before"id="before-start-2">
<h3>Before you start</h3>
<ul>
<li><strong>Node.js 18 or newer.</strong> Check with <code>node --version</code>. No Node? Get it from <ahref="https://nodejs.org/">nodejs.org</a> (the LTS download), or run <code>winget install OpenJS.NodeJS.LTS</code> on Windows, <code>brew install node</code> on macOS, or use <code>nvm</code> on Linux. Then open a new terminal.</li>
<li><strong>Start from your project.</strong> Open your terminal in the project you want to work on (<code>cd</code> into it) before you run anything. Plan2Code works on the folder you start it in.</li>
<li><strong>Ways in.</strong><code>plan2code</code> (Claude Code, Devin or Codex), or type <code>/plan2code</code> in your agent (<code>$plan2code</code> in Codex).</li>
<pclass="then">then, from your project, run <code>plan2code</code> (Claude Code, Devin or Codex), or type <code>/plan2code</code> in your agent (<code>$plan2code</code> in Codex).</p>
<pclass="then">It always opens a menu; no output at all means npm could not reach the repository and hid the reason: <code>git ls-remote https://github.com/jparkerweb/plan2code.git</code> shows why.</p>