---
model: sonnet
---

# /tas-spec $ARGUMENTS

Create lightweight spec before coding — for solo dev, prototype, spike, internal tool.
Differs from `/tas-fix`: has spec document, suitable for tasks > 2 hours or needs AC tracking.

## Steps

### 1 — Gather information
`$ARGUMENTS` is task description. If not clear enough, ask max 3 questions:
- **Goal**: What to build? What problem to solve?
- **AC**: What does done look like? (2-5 specific, testable criteria)
- **Constraints**: Tech constraints, out of scope?

Don't ask if $ARGUMENTS is already clear enough.

### 2 — Create SPEC.md
Create file `SPEC.md` at project root:

```markdown
# {Title}
> {one-line summary}

**Status:** Draft | **Date:** {today}

## Goal
{Problem to solve — not solution}

## Acceptance Criteria
- [ ] {Given/When/Then or testable statement}
- [ ] ...

## Out of Scope
- {What won't be done}

## Constraints
{Tech constraints, patterns to follow — omit if none}

## Open Questions
{Unanswered questions — omit if none}
```

### 3 — Next step
> "SPEC.md created.
> - Plan in detail: `/tas-plan SPEC.md`
> - Code immediately: `/tas-dev` (requires `require_plan: false` in tas.yaml)"

## Principles
- SPEC.md is single source of truth — don't create additional files
- Keep short: target < 1 page
- If AC > 8 items or task > 1 day → suggest using `/tas-feature` instead