원클릭으로 Manus에서 모든 스킬 실행

orch-build-mvp

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.

Manus에서 실행

스타212,062

포크32,560

업데이트2026년 6월 7일 08:15

출처

affaan-m

affaan-m/ECC

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

SKILL.md

readonly

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.

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

Run the orch-pipeline engine with the settings above.
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.
Stop at Gate 1 (slice plan) and Gate 2 (pre-commit). Commit the scaffold and each slice as separate feat: commits.
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

이 저장소의 다른 Skills

같은 저장소

continuous-learning-v2

affaan-m/ECC

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

2026-06-10212.1k

orch-add-feature

affaan-m/ECC

Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.

2026-06-07212.1k

orch-change-feature

affaan-m/ECC

Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.

2026-06-07212.1k

orch-fix-defect

affaan-m/ECC

Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.

2026-06-07212.1k

orch-pipeline

affaan-m/ECC

Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

2026-06-07212.1k

orch-refine-code

affaan-m/ECC

Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.

2026-06-07212.1k

orch-build-mvp

Actor · action · target: orch · build · mvp. Thin wrapper over the shared engine in orch-pipeline.

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

Run the orch-pipeline engine with the settings above.

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.

Stop at Gate 1 (slice plan) and Gate 2 (pre-commit). Commit the scaffold and each slice as separate feat: commits.

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