verify
Verify implementation against change artifacts using four dimensions. Uses independent subagents to eliminate context bias.
Dispatch the verification subagent AND code-reviewer in parallel — they are independent checks.
If a subagent fails, proceed with findings from the other. If BOTH fail, report the failure — do NOT fall back to self-verification.
Rationalization Prevention
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
23apply
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
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