project-standart-epic

<when_to_use> After architecture, before decomposition into tasks When implementation must be ordered by value, risk, and dependencies </when_to_use>

<required_preload> shared-base-rules shared-docs-paths planning-change-inventory planning-scope-minimization planning-estimation </required_preload>

<document_target> Create/update files in epics/{epic key}-{epic number}-{user friendly name}.md </document_target>

<output_format>

<quality_rules> No epics without linkage to requirements or architectural necessity Epic boundaries are narrow enough for manageable delivery Execution order accounts for the critical path </quality_rules>