| name | spectra-planning |
| description | Decision-ready specifications via the SPECTRA cycle. Use for complex features (complexity ≥7/12), multi-component/service changes, ambiguous requirements needing structured decomposition, or any task where 'just start coding' would require significant rework. Produces a dual-format spec (Markdown + YAML/JSON), never code. |
| methodology | SPECTRA |
| methodology_version | 4.2 |
SPECTRA — Planning Skill
Use this skill when the user needs a specification before implementation.
Activation signals
- Complex features (complexity ≥7/12 on the SPECTRA rubric)
- Multi-component or multi-service changes
- Ambiguous requirements needing structured decomposition
- Specification refinement needing deliberate process
- Any task where "just start coding" would likely require significant rework
The cycle
CLARIFY → Scope → Pattern → Explore → Construct → Test → Refine → Assemble
READ-ONLY during all phases — produce specifications, never code.
Progressive disclosure
This SKILL.md is the routing card. Escalate on demand:
.eidolons/spectra/SPECTRA.md — full cognitive architecture.eidolons/spectra/scoring.md — scoring rubrics and matrices.eidolons/spectra/templates.md — output formats per phase.eidolons/spectra/templates/planning-artifact.md — spec artifact template
Hard constraints (P0)
- READ-ONLY. No code, no file edits, no mutations. Plans only.
- Dual-format output: human-readable Markdown + agent-executable YAML/JSON.
- Never skip CLARIFY. Parse WHO / WHAT / WHY / CONSTRAINTS before planning.
- Complexity ≥7/12 → extended thinking (2× token budget).
- Confidence <85% at Assemble → return to Refine (max 3 cycles).
- Output is a specification. Execution belongs to a separate agent.
- Every output path lives under
.spectra/ — plans at .spectra/plans/, state at .spectra/state/, logs at .spectra/logs/. Never scatter files outside .spectra/.
On activation
Load .spectra/setup/spectra-conventions.md if it exists. When present, its project vocabulary (real module names, test framework, deploy targets) supersedes SPECTRA's generic placeholders. When absent, continue with generic defaults — the conventions file is optional enrichment, not a prerequisite.
SPECTRA v4.2.8
