Stats
Actions
Tags
From ecc
Bootstraps a working MVP from a design/spec doc by ingesting, slicing, scaffolding, TDD-building via GAN harness, reviewing, and gated committing.
How this command is triggered — by the user, by Claude, or both
Slash command
/ecc:orch-build-mvpThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /orch-build-mvp Manually launch the **orch-build-mvp** orchestrator: turn an SDD/PRD/system-design document into a running vertical slice. ## Usage Examples: ## What It Does Invoke the `orch-build-mvp` skill with `$ARGUMENTS` as the doc path. The skill (via the shared `orch-pipeline` engine, full pipeline incl. Scaffold) will: 1. Read the spec; extract scope, locked decisions, and a feature list ordered as **thin vertical slices** (one end-to-end path first). → **GATE 1** (approve slice plan). 2. Scaffold the first end-to-end slice. 3. Reuse the GAN harness: translate the SDD in...
Manually launch the orch-build-mvp orchestrator: turn an SDD/PRD/system-design document into a running vertical slice.
/orch-build-mvp <path to design/spec doc>
Examples:
/orch-build-mvp civicpulse/docs/SDD-v0.6.md
Invoke the orch-build-mvp skill with $ARGUMENTS as the doc path. The skill
(via the shared orch-pipeline engine, full pipeline incl. Scaffold) will:
gan-harness/spec.md +
eval-rubric.md, then drive /gan-build "<brief>" --skip-planner
(generator → evaluator loop) until the score passes or plateaus.code-reviewer (+ security-reviewer on any security-trigger slice), then
commit the scaffold and each slice as separate feat: commits. → GATE 2.If $ARGUMENTS is empty, ask the user for the path to the design/spec doc.
npx claudepluginhub affaan-m/ecc --plugin ecc/pipelineOrchestrates end-to-end feature development pipeline for small/medium features (spec → plan → build → test → review → ship), producing mergeable vertical slices.
/designExecutes a multi-phase structured development workflow with parallel agents, tracked milestones, and phase-level risk management.
/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/developRuns 6-phase SDLC pipeline (Discovery to Summary) for feature development, producing plans, code, and summaries. Supports --plan-only, --auto, resume from @path, and --verify-arch/impl flags.
/bmad-pilotOrchestrates AI development team to build project from description, with repo scanning, architecture, planning, coding, and QA phases plus user confirmations. Options: --skip-tests, --direct-dev, --skip-scan.