Stats
Actions
Tags
From builders-dont-cry
BDC execute: execute an approved plan with fresh evidence.
How this command is triggered — by the user, by Claude, or both
Slash command
/builders-dont-cry:executecommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
<!-- BDC managed command --> # /execute ## Contract Execute exactly one approved atomic step or approved plan path with fresh evidence. ## Runtime Use core/skills/execute/SKILL.md. Resolve active plan with bdc plan resolve, create step packets, then run bdc execute --plan <plan> --step <id>. If the Skill tool is available, run the `execute` skill and pass through `$ARGUMENTS`. If the Skill tool is unavailable, follow `core/skills/execute/SKILL.md`. ## Required Evidence Attach command results, scope checks, progress dashboard state, and completion evidence for each passed step. ## St...
Execute exactly one approved atomic step or approved plan path with fresh evidence.
Use core/skills/execute/SKILL.md. Resolve active plan with bdc plan resolve, create step packets, then run bdc execute --plan --step .
If the Skill tool is available, run the execute skill and pass through $ARGUMENTS. If the Skill tool is unavailable, follow core/skills/execute/SKILL.md.
Attach command results, scope checks, progress dashboard state, and completion evidence for each passed step.
Stop if scope changes, evidence cannot be produced, or execution requires an unapproved architecture or dependency change.
.bdc/ or ${BDC_HOME:-$HOME/.bdc} for plans, handoffs, events, and evidence.npx claudepluginhub 0xmariowu/builders-dont-cry/executeExecutes specific tasks from Kiro specs with focused implementation for developer assistance. Accepts feature name and task description or number.
/executeDispatches a single roadmap step to a specified agent for TDD execution, extracting context from roadmap.json, applying rigor profile, and updating execution-log.json.
/executeExecutes implementation plans systematically: loads plan, runs tasks in dependency order with checkpoints, validates against criteria, tracks progress, and reports metrics. Supports --task, --resume, --phase options.
/executeExecutes development tasks in adaptive parallel waves with code review, quality gates, E2E checks, and task adaptation for spec-compliant complete implementations.
/executeExecutes validated plans using isolated agents for tasks, spec review, code review, and conflict resolution, with human checkpoints between batches. Supports --resume, --status, --dry-run, and other flags.
/executeExecutes an implementation plan from plans folders. Lists incomplete (DRAFT/APPROVED/IN_PROGRESS) plans for selection if no path provided, reviews, preps worktree for large tasks, runs autonomously.