spec-recipes

Files (1)

• SKILL.md

SKILL.md (first lines)

# Spec recipes

Full definitions: `SPECFORGE_HOME/ENGINEERING-RECIPES.md` (§0 + matrix).  
Orchestrator: `agents/eng-orchestrator.md`. Playbook: `SPECFORGE_HOME/ENGINEERING-PLAYBOOK.md`.

**No default production recipe.** Classify need → smallest recipe × tier → matrix R/O/—.

## Rules

1. Build from **minimal + matrix R/O/—**, not maximal ASCII pipelines.
2. **Reclassify** when evidence changes; announce before continuing.
3. HANDOFF must include: `Recipe`, `Tier`, `Need summary`, `Plan (R/O/skipped)`, `Adapt watchers`, `parent_REQ` when relevant.
4. Conflict with other docs: **recipes omit wins** unless checklist flags risk.
5. Human owns `APPROVED` / BUG `Human ACK` / override / Critical & Blocking-drift waivers. Loops ≤2 rounds.
6. **Two-pass:** planning agents only → Phase `awaiting-human` (user edits disk) → implementation agents. Chat LGTM ≠ APPROVED. `READY_FOR_APPROVAL` is HANDOFF-only.

## Quick picker (after need checklist)

| Need | Recipe |
|------|--------|
| Spike / should we | Tier 0 note or `advisory-only` |
| Docs only | `docs-touch` |
| Vendor sync | `vendor-sync` |
| Specs only | `spec-only` |
| New product | `new-application` |
| New user-facing capability | `greenfield-feature` (`capability`) |
| Defect, normal | `bug-fix` |
| Prod-urgent | `hotfix` |
| Deps/refactor | `maintenance` |
| IaC/CI/env | `infra-change` |
| CVE / security | `security-patch` |

## Gates (only those implied by **R** agents)

| Gate | When required |
|------|----------------|
| G-plan | Planning agents finished; files may still be DRAFT/OPEN |
| G-human | User set disk `Status: APPROVED` or BUG `Human ACK: APPROVED` before coding |
| G1 REQ user-APPROVED | Before architect / implementers per matrix |
| G2 ARCH user-APPROVED | When ARCH is **R** for this tier |
| G3 tests + Critical-clear | Before verifier when test/review are **R** |
| G4 verify + Blocking drift clear | Before DONE when verifier/guardian are **R** |

## Minimal examples (not ceilings)

- **Capability Tier 1:** REQ → **user APPROVED** → implementer → test-runner → verifier
- **Bug-fix Tier 1:** debugger (BUG) → implementer → test-runner → code-reviewer → verifier
- **Hotfix:** debugger → implementer → test-runner → verifier (+ security if adjacent)

Full ASCII of every agent is a **Tier 3 ceiling**, not the default. See recipes matrix.

## Principle 8

After each gate: update specs + memory (include **agents_planned**) → optional GATE file → **fresh subagent** with paths only. Never attach chat summaries.

## Invoke

```
/eng-orchestrator — diagnose need, then minimal recipe × tier plan
```

Alias command `/spec-pipeline` opens this same skill (entry cheat sheet).

## Related skills

| Skill | Role |
|-------|------|
| `spec-req-author` / `spec-arch-author` | Write DRAFT specs |
| `spec-challenger` | Adversarial review (capped) |
| `spec-handoff` | End-of-phase HANDOFF |
| `spec-verifier` / `spec-guardian-drift` | Verify / drift |
| `spec-token-budget` / `spec-advisory` / `spec-vendor-sync` | Token / meta |
| `ponytail` / `ponytail-review` | Minimal code / Gate 3 bloat |

From sushilti80/specforge-engineering-team, MIT.

More from sushilti80/specforge-engineering-team