speclisted
Install: claude install-skill epicsagas/epic-harness
# Spec — Define What to Build
**CRITICAL**: Run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory.
## Process
1. **Understand the request**
- Read any existing context (CLAUDE.md, README, codebase structure)
- If the request is vague, ask focused questions (max 3 at a time)
- Never assume — clarify ambiguity before proceeding
2. **Produce the spec**
Write a concise spec covering:
- **Goal**: One sentence — what does this achieve?
- **Scope**: What's included and explicitly excluded
- **Requirements**: Numbered list (`R1`, `R2`, ...) of concrete, testable behaviors
- **Acceptance criteria**: Numbered list (`AC1`, `AC2`, ...) — observable outcomes that prove each requirement is met
- **Technical notes**: Constraints, dependencies, edge cases
3. **Confirm with user**
Show the spec in digestible chunks. Get explicit approval before proceeding.
## Output
Save the approved spec to `$HARNESS_DIR/specs/SPEC-{timestamp}.md` using this exact format:
```markdown
---
status: approved
created: {ISO-8601 timestamp}
goal_slug: {kebab-case-goal-summary}
---
# SPEC-{timestamp}: {Goal}
## Goal
{One sentence}
## Scope
- In: {what is included}
- Out: {what is explicitly excluded}
## Requirements
- R1: {concrete testable behavior}
- R2: {concrete testable behavior}
## Acceptance Criteria
- AC1 (R1): {observable outcome proving R1}
- AC2 (R2): {observable outcome proving R2}
## Technical Notes
{Constraints, dependen