Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/spec-guard:spec-grind PATH_TO_SPEC [--verify COMMAND] [--max-iterations N]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Spec Grind Execute the setup script to start the grinding loop: Implement every requirement in the spec. After each implementation pass, run the verification command (if provided) and check results. The Stop hook will prevent exit and re-inject the spec until all requirements are met. CRITICAL: Output <promise>SPEC_COMPLETE</promise> ONLY when every requirement in the spec is implemented and verified. Do not output a false promise to exit the loop. Approach: 1. Read the full spec 2. List all requirements not yet implemented 3. Implement the next requirement 4. Run the verification c...
Execute the setup script to start the grinding loop:
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-grind.sh" $ARGUMENTS
Implement every requirement in the spec. After each implementation pass, run the verification command (if provided) and check results. The Stop hook will prevent exit and re-inject the spec until all requirements are met.
CRITICAL: Output SPEC_COMPLETE ONLY when every requirement in the spec is implemented and verified. Do not output a false promise to exit the loop.
Approach:
npx claudepluginhub travis-gilbert/claude-marketplace --plugin spec-guard