apply
Implement code based on the change artifacts. Supports two modes:
- Gherkin-driven (default): feature files drive implementation and testing
- Proposal-driven: when gherkin is skipped (technical changes), proposal drives testing
<decision_boundary>
Use for:
- Implementing code for a Beat change that has spec artifacts (gherkin or proposal) done
- TDD implementation driven by feature files or proposal risk points
- Resuming implementation of a partially completed change
NOT for:
- Creating spec artifacts like proposal, gherkin, or design.md (use
/beat:design) - Breaking down tasks or creating execution plans (use
/beat:plan) - Verifying implementation completeness (use
/beat:verify) - Exploring ideas or investigating a problem (use
/beat:explore)
More from kirkchen/beat
distill
Use when extracting BDD specs from existing code — for adopting Beat in an established codebase or distilling a module into feature files
24archive
Use when finalizing a Beat change — syncs features to living documentation and archives the change — not for verifying implementation
23verify
Use when validating implementation completeness before archiving a Beat change
23explore
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change
23design
Use when designing a Beat change — creates change container and generates spec artifacts (proposal, gherkin, design.md) — not for task breakdown or implementation
23setup
Use when setting up Beat for the first time in a project or updating project configuration — not for editing beat/config.yaml directly or configuring non-Beat tools
23