---
description: Start spec-driven development by writing a structured specification before code
---

Invoke the `spec-driven-development` skill via the `skill` tool.

Begin by understanding what the user wants to build. Ask clarifying questions about:

1. The objective and target users.
2. Core features and acceptance criteria.
3. Tech stack preferences and constraints.
4. Known boundaries: what to always do, ask first about, and never do.

Then generate a structured spec covering objective, commands, project structure, code style, testing strategy, and boundaries.

Confirm with the user before saving, then save the spec to the location the `spec-driven-development` skill defines (default `docs/prds/{area}/PRD{n}-{topic}.md`; overridable per project via `.ai/agent-skills-overrides.md`).
