beat

Use when implementing a Beat change — requires gherkin or proposal artifact to be done first

Use when a Beat change is complete (implemented, or distilled and verified) and ready to archive — not for verifying implementation

Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration

Use when extracting BDD specs from existing code — for adopting Beat in an established codebase or distilling a module into feature files

Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change

Use when breaking down a Beat change spec into tasks — not for spec creation or implementation

Use when initializing Beat or updating its config — not for editing config.yaml directly or non-Beat tools

Use when validating implementation against spec artifacts before archive — not for design, planning, or implementation