brieflisted

@.claude/shirabe-extensions/brief.md @.claude/shirabe-extensions/brief.local.md # Brief Documents BRIEF documents frame a single named feature before its requirements exist. They sit in the tactical chain between ROADMAP (which sequences which features get built and in what order) and PRD (which captures what one feature does and why). A ROADMAP entry is a line item; a PRD is a requirements contract. The BRIEF is the framing step in between: it states the problem the feature solves, the outcome a user should experience, the concrete journeys that exercise it, and the boundary of what it holds in and pushes out — in a form the downstream PRD can pick up directly. A BRIEF frames one feature, so it has no altitude band to police and no falsifiable bet to invalidate. That is why the brief workflow is the strategy workflow minus the altitude reviewer, the visibility-gated section, and the Sunset lifecycle state. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Durable. Stays in `docs/briefs/` after completion. BRIEF is durable because the framing of a feature — the problem, outcome, journeys, and scope boundary — stays in the audit trail. Future readers tracing why a feature was scoped need the BRIEF to remain in place even after the feature ships. ## Brief Format See `references/brief-format.md` for the full format specification: frontmatter schema, required and optional sections, section matrix, content boundarie