Decision 0041 · Accepted
Product alignment
skill
Flow checks alignment at three scopes already: tldr checks a session against its goal, review checks a change against its spec, and flow keeps root docs current with the code.
- Status
- Accepted
- Built from:
- da88c48
Status: Accepted (2026-10-28). Grows the catalog under the rule in PRODUCT.md that further catalog growth needs its own decision. Related: 0005 (tldr session alignment), 0008 (visual summaries stay in tldr), 0009 (adopter PRODUCT.md is that product).
Context
Flow checks alignment at three scopes already: tldr checks a session against its goal, review checks a change against its spec, and flow keeps root docs current with the code. Nothing steps back to ask whether the product as a whole still serves its vision, users' problems, and success metrics. That question comes up after several shipped specs, when drift and accreted complexity are invisible from inside any one change.
Decision
Add an align skill (Product discovery group, since its priorities feed the next discovery bet; thinking tier). On "are we building the right thing", align compares the product's intent (PRODUCT.md, DESIGN.md, accepted specs and decisions, roadmap) with what the code actually implements.
- Read-only. It reports;
flow,explore,to-spec, orgrillact on what it finds, only when asked. - What and why, not how. Code quality stays with
review. - Evidence over documents. Code decides what is implemented; documents decide what was intended; planned work is labelled as planned.
- Visual and short. A journey-to-capability map, then working, missing, drift, and complexity, ending in up to three ranked priorities. No artifact is written.
Alternatives
- Extend
review. Rejected: review is scoped to a change and its spec, runs per-axis workers, and gatesship; a product-wide check would make it heavier and blur its scope. - Extend
tldr. Rejected:tldrsummarizes named material or a session; judging the product against its metrics needs reading code and intent, which would change what "tldr" means. - Extend
explore. Rejected:explorelooks forward, ends in a brief, and commits on anexplore/branch;alignjudges what is already built against intent and writes nothing. - Extend
flow. Rejected:flowedits root docs to match the product;alignquestions whether the product matches the docs, and must stay read-only.
Consequences
- The catalog grows by one skill:
scripts/validate.mjs,docs/skills.md,README.md, andPRODUCT.mdlistalign. alignneeds no Git and writes nothing, so it joins the thinking tier.GLOSSARY.mddefines product alignment apart from context alignment (flow), session alignment (tldr), and alignment review (review).