spec-writer

# Spec Writer

Interactive specification writer that transforms ideas into actionable implementation plans through collaborative dialogue.

## Arguments

- `topic` (positional): The topic or idea to write a spec for
- `--mode=<interactive|autonomous>`: Operating mode (default: interactive)
- `--services=<svc1,svc2>`: Limit spec to specific services
- `--template=<path>`: Use a custom template file
- `--output=<path>`: Override output location

## Configuration

Check for `.claude/spec-workflow/config.yaml` in the project:

```yaml
paths:
  specs: "./specs"              # Where specs are saved

services:                       # Your technology stack (optional)
  backend:
    path: "./backend"
    patterns: "./backend/AGENTS.md"  # Architecture docs to reference
  frontend:
    path: "./frontend"

spec:
  naming: "{date}-{topic}-spec.md"   # Spec file naming pattern
```

### Philosophy Injection

If `.claude/spec-workflow/philosophy/spec-standards.md` exists, read it and incorporate its guidance. This file contains the user's standards for what makes a good spec.

### Template

Use template from (in priority order):
1. `--template` argument
2. `.claude/spec-workflow/templates/spec.md` in project
3. Built-in template (see references/spec-template.md)

---

## Modes

This skill operates in three modes:

### Interactive Mode (Default)

**Trigger:** User invokes spec-writer directly

- Full dialogue with user
- Validation checkpoints after each phase
- Questions asked one at a time
- User confirms design decisions

Announce at start: "I'm using the spec-writer skill to create the implementation plan."

### Autonomous Mode

**Trigger:** Invoked by spec-orchestrator with `{ mode: "autonomous", request: string }`

- Makes design decisions independently
- No validation checkpoints
- Documents reasoning for decisions made
- Produces complete spec in one pass

Announce at start: "I'm writing a spec autonomously for orchestrator review."

### Revision Mode

**Trigger:** Invoked