Specify

Capture feature intent and acceptance criteria before planning begins. Writes docs/specs/_/spec.md and stops — the user must approve the spec before the plan skill runs.

Doc paths

Default convention: specs live under docs/specs/. Check the project's CLAUDE.md for an overriding location (e.g. a "Docs Layout" section or explicit mention of spec paths) before falling back to the default.

Spec Identifier Derivation

1. Use Glob with pattern docs/specs/*/*.md to list existing spec folders — do NOT use a trailing-slash pattern (docs/specs/*/) or a bare docs/specs/*, both silently return nothing on Windows; the nested */*.md form matches files one level down and works
2. Generate the current local timestamp as YY_MM_DD_HH (for example, 26_07_18_14)
3. Combine it with a short kebab-case feature name: _
4. Do not derive or assign a numeric index

Orchestration

Spawn an architect sub-agent (general-purpose) briefed with:

• The user's feature description
• Relevant project rules from CLAUDE.md and any project rules directory
• The output path: docs/specs/_/spec.md
• The spec format below

The architect writes the spec file directly. You (orchestrator) then:

1. Present the spec contents to the user
2. Collect feedback and re-brief the architect if changes are needed (iterate until the user approves)
3. Stop. Do not run the plan skill or write any code. The user must explicitly request the next step.

Spec Format

# Spec: 

## Feature Intent

As a , I want , so that .

## Acceptance Criteria

- **Given**  **When**  **Then** 
- (one bullet per observable behaviour; cover the happy path and the most important edge cases)

## Out of Scope

- (explicit exclusions — things the feature deliberately will not do)

## Ambiguities

- [NEEDS CLARIFICATION: ]
- (omit this section entirely if there are no ambiguities)

Rules

• Do NOT write any plan, code, or assets — only the spec document.
• Use [NEEDS CLARIFICATION: …] markers freely — surfacing unknowns early is the point.
• The spec folder name starts with its creation timestamp and uses a kebab-case name: docs/specs/26_07_18_14_my-feature/spec.md.
• Do not create plan.md in the spec folder — that is the plan skill's job.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: KonH
• Source: KonH/ClaudeTools
• License: MIT

Install and usage instructions live in the source repository linked above.