mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-14 07:13:35 +08:00
90dfd9505d
* feat: add orch-* orchestrator skill family Lightweight wrappers that orchestrate existing ECC agents through a gated Research -> Plan -> TDD -> Review -> Commit pipeline, right-sized per task. - orch-pipeline: shared engine (phases, size classifier, two gates, agent map) - orch-add-feature/change-feature/fix-defect/refine-code/build-mvp: thin wrappers delegating to the engine * chore: register orch-* family in catalog, command registry, and agent.yaml (post-rebase onto green main) --------- Co-authored-by: ECC Test <ecc@example.test>
49 lines
2.3 KiB
Markdown
49 lines
2.3 KiB
Markdown
---
|
|
name: orch-build-mvp
|
|
description: Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
|
|
origin: ECC
|
|
---
|
|
|
|
# orch-build-mvp
|
|
|
|
Actor · action · target: **orch · build · mvp**. Thin wrapper over the shared
|
|
engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
|
|
|
|
## When to Use
|
|
|
|
- The user has a **design / spec document** (SDD, PRD, system_design) and wants a
|
|
working vertical slice bootstrapped from it.
|
|
- Takes a doc path as its argument, e.g. `civicpulse/docs/SDD-v0.6.md`.
|
|
|
|
## Operation settings
|
|
|
|
- **Default size floor:** large — this is the full pipeline including Scaffold.
|
|
- **Phase mask:** 0 (read the spec) → 1 → 2 (heavy) → 3 (scaffold) → 4 → 5 → 6.
|
|
- **First move (phase 0 → 2):** read the doc; extract scope, locked decisions,
|
|
and the feature list; order it into **thin vertical slices** (one end-to-end
|
|
path first, not all-models-then-all-views). Phase 3 stands up that first slice.
|
|
|
|
## How It Works
|
|
|
|
1. Run the `orch-pipeline` engine with the settings above.
|
|
2. **Reuse the existing GAN harness** instead of hand-rolling an iterate loop:
|
|
- Translate the SDD into `gan-harness/spec.md` + `gan-harness/eval-rubric.md`
|
|
(this stands in for what `gan-planner` would generate — you already have the spec).
|
|
- Drive the build with `/gan-build "<one-line brief>" --skip-planner`
|
|
(defaults: `--max-iterations 15`, `--pass-threshold 7.0`,
|
|
`--eval-mode playwright`; use `--eval-mode code-only` for non-UI slices).
|
|
- That command runs the `gan-generator` → `gan-evaluator` loop and writes
|
|
`gan-harness/feedback/feedback-NNN.md` until the score passes or plateaus.
|
|
3. Stop at **Gate 1** (slice plan) and **Gate 2** (pre-commit). Commit the
|
|
scaffold and each slice as separate `feat:` commits.
|
|
4. Add `security-reviewer` for any slice touching a security trigger.
|
|
|
|
## Example
|
|
|
|
```
|
|
orch-build-mvp: civicpulse/docs/SDD-v0.6.md
|
|
→ read SDD → slice list (vertical) → scaffold slice 1 [GATE 1: approve]
|
|
→ /gan-build --skip-planner (generator → evaluator loop) scores vs spec → review
|
|
→ commit feat: [GATE 2: confirm] → next slice
|
|
```
|