Ace Build Checklists

A simple path from product brief to design, requirements, and a finished build.

Build Checklists is a four-stage pipeline for building features without wasting effort on bad ideas, vague designs, or rushed execution:

Brief  →  Design  →  Requirements  →  Build
Stage What it answers Output
PB (Product Brief) Should we do this? One page: what / problem / solution / why this solution
DD (Design Doc) What does it look like? Before/after state, HTML visual charts
PRD (Requirements) How do we get it built well? A runnable build checklist
Build Build it. Working feature, checklist marked off

Why this pipeline

Most building goes wrong in one of three places, and each stage exists to catch one of them:

  1. The wrong thing gets built: fix with the PB. One page, no more; if it doesn’t fit on a page, the idea isn’t clear yet.
  2. The right thing is poorly designed: fix with the DD. Generate before and after diagrams as dependency-free HTML files, so the new behavior is obvious before anyone writes code.
  3. The right thing, well designed, is sloppily executed: fix with the PRD. The PRD is a checklist, not a spec. Prose PRDs read like reading material, and on a build day you skim them and skip steps. Checklists are runnable; when you tick boxes, you don’t skip.

Scale the pipeline to the change: major work runs all four stages, medium work can skip the DD, small-but-significant work can go PB → Build, and small fixes just get built. For work that needs a checklist, keep it short and specific.

How to use it

Get the checklists through Ace, then copy the _templates/ folder into your workspace. Use them with an AI coding tool such as Claude Code or Codex. The CLAUDE.md snippet is an optional Claude Code integration; adapt those instructions to your tool. For each feature, create a numbered folder - 001-feature-name/ - and drop in PB.md, then DD.md if needed, then PRD.md. Work the checklist top to bottom; when the last box is checked, the feature ships. MIT licensed.

← All resources