One-Pager Brief
Create a single-page brief or summary that fits one printed page and lands one message fast — a product one-pager, executive summary, project brief, or leave-behind. Scopes the single audience + the one thing they must remember FIRST, then designs a tight one-page layout (headline, scannable sections, a sidebar of facts), then writes punchy copy that fits the page — ruthless about cutting anything that pushes past one page. Use when the answer must be skimmable in 60 seconds on a single sheet.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the briefplannerentry
one audience, one takeaway, the must-include facts
Show working prompt
Constrain hard — this is ONE page. Step 1: name the single audience and the one sentence you want them to remember after reading. Step 2: list the must-include facts and cut everything else; a one-pager that needs two pages has failed scoping. Step 3: choose the section set that fits one page: a headline + subhead, a short context paragraph, 3-4 scannable value/benefit points, and a small facts/contact sidebar (stats, pricing, links). Step 4: set a word budget per zone (e.g. subhead <= 15 words, each point <= 20 words) so the page cannot overflow. Step 5: write an acceptance-criteria checklist ('fits on one printed page', 'headline states the one takeaway', '3-4 scannable points, each one line', 'a facts/contact block is present', 'no section exceeds its word budget'). Write the scope + word budgets + checklist via write_task_note AND to notes/scope.md. No layout or final copy yet. - Design the layoutdesigner
one-page grid: headline band, columns, fact sidebar, print rule
Show working prompt
Design a layout that physically fits one page. Step 1: choose page size (Letter/A4 via @page) with tight margins and a single visual hierarchy: a headline band at top, a main column for the points, and a narrow sidebar for the facts/contact block. Step 2: pick a palette with exact hex (ink, background, one accent) and a type scale where the headline dominates and body stays compact. Step 3: define how the 3-4 points render (icon-less bullets or small labeled blocks) and how the sidebar facts render (label + value rows). Step 4: set the print rule so the whole thing is exactly one page — constrain total height and use break-inside:avoid. Step 5: write a visual-criteria checklist ('single page, no overflow', 'headline is the dominant element', 'sidebar visually distinct from main column', 'consistent accent color'). Write the layout spec + checklist via write_task_note AND to notes/design.md. No copy yet. - Write and assemblecopywriter
write punchy copy into index.html within the page + word budgets
Show working prompt
Write the copy and assemble it into the one-page layout as a single self-contained index.html (inline CSS with the @page/print rule). Step 1: write a headline that states the one takeaway and a subhead within its word budget. Step 2: write the short context paragraph and the 3-4 value points, each one line within budget — punchy, benefit-led, no filler. Step 3: fill the facts/contact sidebar with the must-include facts as label/value rows. Step 4: drop everything into the locked layout with the exact palette and type scale; confirm it occupies exactly one page (trim copy if it overflows — cutting words is the job, not adding pages). On a loop-back, fix ONLY the named gaps. Write the path + a note confirming it fits one page via write_task_note.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
QA the one-pager. Step 1: open/render index.html and, if print-preview is available, confirm it is EXACTLY one page with no overflow onto a second sheet. Step 2: check EACH acceptance criterion: headline states the one takeaway, there are 3-4 scannable one-line points, a facts/contact block is present and visually distinct, no zone exceeds its word budget, the accent color is consistent and the headline dominates. Step 3: read it as the target audience and confirm the one message lands in under 60 seconds. Write PASS/FAIL per criterion; if it overflows one page, FAIL the page-fit criterion and loop back to trim. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "write" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- one pager
- one-page brief
- executive summary
- leave behind
- product one sheet
- make a one page summary
Source
View this craftbook on GitHub · MIT license