Decision 0010 · Accepted
Optional start
skill authorized
0009-adopter-product-context.md (accepted, immutable) states that an adopter's PRODUCT.md is that product's identity, that flow is not project initialization, and that this repository must not ship flow start or adopter instruction-file edits in that change.
- Status
- Accepted
- Built from:
- da88c48
Amended by 0020: the opt-in Flow block is the one allowed adopter instruction-file edit.
Context
0009-adopter-product-context.md (accepted, immutable) states that an adopter's PRODUCT.md is that product's identity, that flow is not project initialization, and that this repository must not ship flow start or adopter instruction-file edits in that change. The same record left unresolved whether a later, explicit, optional start skill should exist.
The Flow ecosystem alignment interview (decisions 02–33) and spec 005 require a way for adopters to choose flow-next or flow-mono, initialize a project, and create product-specific root docs without copying Flow's methodology identity or mandating a Flow pipeline.
Decision
- Authorize a future, optional, manually invoked skill named
startin flow-skills (notflow startas a leading word or discoverable alias for Flow Lite). - The skill may help select
flow-nextorflow-mono, initialize from the chosen template, handle naming and Git initialization as appropriate, and create project-specificPRODUCT.md,DESIGN.md,ARCHITECTURE.md, andGLOSSARY.mdfor that product. - The skill must not copy Flow's product identity into adopter documentation; must not edit adopter
AGENTS.mdor equivalent; must not introduce a mandatory Flow runtime or implicit orchestration; must remain agent- and UI-agnostic. - Shipping the skill is a separate increment (catalog growth to fifteen skills, tests, and docs). This decision does not add the skill by itself.
- Until
startships,flow,implement, andreviewcontinue to refuse unauthorized scaffolding. Discoverableflowremains alignment only.
Rationale
GitHub Use this template remains valid without the skill. A dedicated optional skill reduces mistaken "start project" invocations of Flow Lite and documents the approved initializer behavior in one place, consistent with 0009's product-context rules.
Alternatives
- Leave initialization entirely to GitHub templates and adopter work (status quo before skill ships).
- Bundle initialization into Flow Lite (
flow) — rejected; conflates alignment with scaffolding.
Consequences
- Update PRODUCT.md, GLOSSARY.md, agent-compatibility.md, and boundary text in
flow,implement, andreviewskills to reference this decision instead of an "open" initializer question. - 0009 is not edited and not superseded; this record resolves its unresolved paragraph only.
- Validator skill count stays fourteen until the
startskill directory exists. - Update (2026-10-27):
skills/start/ships onmain; the validator expects fifteen skills including optionalstart.