# Sdd Specify

> Write or refine spec.md, covering assumptions, acceptance criteria, clarify, and the cold read.

- Skill: `mariano-aguero/sdd-specify` (Agent Skill)
- Install (CLI): `npx get-skill add mariano-aguero/sdd-specify`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mariano-aguero/sdd-specify/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: mariano-aguero (https://skillmd.com/u/mariano-aguero)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/mariano-aguero/sdd-specify

---


# sdd-specify

Paths below are relative to this file. Resolve them before running anything.

Read `../spec-driven-development/SKILL.md`, section "Phase 1".
Read `../spec-driven-development/references/workflow-phases.md`, section "Phase 1" and, for a change to existing behavior, "Delta Specs".
Use "Assumptions Surface Prompt" and "Initial Specification Prompt" in `../spec-driven-development/references/prompt-patterns.md`.
If `spec.md` has open questions, run "Clarify Phase Prompt" and "Post-Clarify Spec Update Prompt" from the same file.
Use the template under "spec.md Template" in `../spec-driven-development/references/artifact-templates.md`.

Produce: `specs/<feature>/spec.md`, MoSCoW-prioritized ACs, each `[MUST]` with a proof line.
Write the draft `spec.md` in this turn. Do not wait for answers first: each assumption you cannot confirm from the repo goes into the spec as a `[NEEDS CLARIFICATION]` marker, and the reply counts them.
If the request touches auth, permissions or billing, write explicit ACs for each role's allowed and denied actions and for every error case.
Open `[NEEDS CLARIFICATION]` items block Gate 1: name each one and how its answer changes the design, and offer to clarify. If the user insists, proceed: replace each marker with an explicit `Assumption:` line in the spec and report it. Never choose silently, never refuse indefinitely.
Cold read (levels M and L): run "Cold Read Prompt" in a fresh agent or session given only `spec.md`, `constitution.md` and the `Baseline:` files of a delta spec, then compare its restatement with the user's intent. List every AC phrase with more than one reading (for example "records belonging to M": created by M, or assigned to M); each is a failing Gate 1 check fixed in the spec. No fresh context available means the cold read is `inconclusive`. Do not mark the spec Approved; the human does.
Gate: "Gate 1" in `../spec-driven-development/references/quality-gates.md`, including the cold read by a reader with no context.
Validate: `node ../spec-driven-development/scripts/sdd-check.mjs specs/<feature>`
Next: `/sdd-plan` once a human approves.
Reply: `Gate 1: pass|fail|inconclusive`, one line per failing check, `ACs: N MUST, N SHOULD, N COULD`, `Open questions: N`, the spec path, and one next action. No preamble, under ~25 lines, never the spec pasted.

