Stats
Actions
Tags
From vcsdd
Approves architect escalation for a phase exceeding iteration limit, resets counter in state.json, records decision in history and resolves escalation file.
How this command is triggered — by the user, by Claude, or both
Slash command
/vcsdd:vcsdd-escalateThe summary Claude sees in its command listing — used to decide when to auto-load this command
## What Approves an escalation when an iteration limit has been exceeded, allowing the pipeline to continue beyond its default cap. This command represents the Architect's explicit decision to grant an exception. ## When Run after `transitionPhase` throws an "Iteration limit exceeded" error. Check `escalations/` directory for the escalation file to review before approving. ## How 1. **Read active feature state.json** 2. **Check escalations/ directory** for pending escalation files 3. **Display the escalation details** (phase, iteration, limit, reason) 4. **Confirm with the user** (in str...
Approves an escalation when an iteration limit has been exceeded, allowing the pipeline to continue beyond its default cap. This command represents the Architect's explicit decision to grant an exception.
Run after transitionPhase throws an "Iteration limit exceeded" error. Check escalations/ directory for the escalation file to review before approving.
state.iterations[phase] to limit - 1 (so the next transitionPhase call will be at exactly the limit)state.phaseHistory: { from: currentPhase, to: currentPhase, timestamp: ..., reason: "Architect escalation approved: <reason>", escalationApproved: true }\n## Resolution\n\nApproved by Architect at <timestamp>. Iteration counter reset to allow one more attempt.\n to the file--phase <phase> — specify which phase to approve (required if multiple escalations pending)--reason <text> — brief justification for the exception (optional, defaults to "Architect approved continuation")/vcsdd-escalate
/vcsdd-escalate --phase 3
/vcsdd-escalate --phase 3 --reason "All prior findings were minor structural issues; core logic is correct"
npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsdd/approveApproves current workflow phase after validation, updates state with timestamp and approver, advances to next phase, auto-executes it, and shows new approval gate.
/fire-autonomousRuns the full build pipeline autonomously — plans, executes, verifies, and advances through all phases without human checkpoints after PRD is complete.
/fast-forwardFast-forwards remaining nWave phases (DISCUSS, DESIGN, DEVOPS, DISTILL, DELIVER) end-to-end without review pauses after user confirmation. Optional feature description or --from flag.
/writ-approveAdvances the current phase of the Writ workflow (design, plan, or tests) using explicit tool-confirmed approval, recording the transition in the session and audit log.
/autonomousExecutes all remaining milestone phases autonomously — discuss, plan, and execute each phase in sequence. Updates ROADMAP.md and STATE.md, creates phase artifacts.
/forgeOrchestrates a feature from raw idea through research, spec, planning, implementation, verification, and release-readiness using configurable phase maps (express/lite/standard/v-model) with human gates and cross-artifact sync-verify.