A blacksmith mid-strike at the anvil with hammer raised, sparks arcing in a glowing trail from a heart-shaped finished piece on the anvil, the workshop doors thrown open behind him revealing a starlit night sky and distant horizon, twin banks of forge fires flanking the scene on either side
Quickstart · Step 3 of 3

Review & Ship

Sweep, review, and ship in 10 minutes.

This covers Steps 4–6: the completeness sweep, independent review, and shipping. For deeper explanations of each step see Chapter 6: Your First Plan.

Before you start: Step 2: Your First Plan is complete, your health endpoint executed and all gates passed.

Step 4: Sweep for Deferred Work

The completeness sweep scans every code file for markers that indicate unfinished work: TODO, FIXME, HACK, stub, placeholder, mock data. For a health endpoint this should return zero.

Terminal
pforge sweep

If the sweep finds any markers, resolve them before continuing. Deferred-work markers are how technical debt silently accumulates, this is where you catch them before they ship.

Step 5: Independent Review

Critical: start a brand-new chat session by clicking the + button. The reviewer must not carry context from the builder, context contamination is the most common source of missed errors.

  1. Select Agent Mode
  2. Attach .github/prompts/step5-review-gate.prompt.md
  3. Replace <YOUR-HARDENED-PLAN> with Phase-1-HEALTH-ENDPOINT-PLAN and send

The review agent checks every change against the Scope Contract: forbidden files not touched, no architecture violations, test coverage meets MUST criteria, no scope creep. For a simple health endpoint, expect a clean PASS.

Shortcut: Select the Reviewer-Gate agent from the agent picker. Same review, with handoff buttons at the end.

Step 6: Ship

One final session (new or continued if context allows) to commit and close out the feature:

  1. Attach .github/prompts/step6-ship.prompt.md
  2. The agent commits using a conventional commit message: feat(health): add GET /health endpoint
  3. Updates docs/plans/DEPLOYMENT-ROADMAP.md to mark the phase complete
  4. Captures a short postmortem for future sessions
Alternatively: ship from the CLI
# Stage everything and commit
git add -A
git commit -m "feat(health): add GET /health endpoint"
git push origin main

What Just Happened

You've completed all 4 sessions of the Plan Forge pipeline:

All 4 sessions complete
Session 1 (Specify & Plan)  ✓  Described the feature; AI structured the plan
Session 2 (Execute)         ✓  AI built it slice-by-slice with gates
Session 3 (Review)          ✓  Fresh AI session audited for drift and errors
Session 4 (Ship)            ✓  Committed, roadmap updated, postmortem captured

The four-session model is deliberate. Each session has a single responsibility and fresh context, the reviewer couldn't carry bias from the builder even if it wanted to. This is what makes the pipeline scale from a health endpoint to a 40-slice refactor.

What's Next

You've run the full pipeline end-to-end. The same process works for any feature, the pipeline scales with the work:

Writing Plans That Work →

Deep dive on scope contracts, slices, validation gates, and stop conditions.
The Dashboard →

Live slice view, cost tracking, traces, and replay — your command desk.
Customization →

Project Principles, profiles, and forge.json — make Plan Forge yours.
What Is Plan Forge? →

The Forge Shop, four stations, and why this architecture works.
A Day in the Forge →

Three worked case studies — the closed loop, the 99-vs-44 A/B test, the quorum run — for context on what just happened.
🎉 Quickstart complete! You've gone from zero to a shipped feature using the full Plan Forge pipeline. Return to Act I any time you want the full depth.