Spec

The Spec phase captures the feature at a high level in plain English.
It focuses on:

What the feature is
Why it exists
How it fits into the product and system
High-level scope and constraints

This is intentionally non-technical and serves as the shared source of truth for intent.

✏️ Steps

Run the /speckit.specify prompt
- /speckit.specify Implement the feature defined in <Jira/GitHub issue link> (and any Figma links or additional context)
- The Agent uses the Atlassian MCP to grab the ticket info (same process for GitHub/Figma, etc).
- This will also run several git commands in the terminal to create a new branch and name it appropriately

Review the output:
- A new feature folder with a spec.md that includes user stories + functional requirements (per the template).
- spec.md is the primary seed document for the entire SDD process. It defines the requirements and feature details at a high level. Be sure to check over this document manually to ensure it’s structured the way you want.
- checklists/requirements.md can be thought of as a type of test document for the specs. It outlines a criterion that the spec should meet, which the agent confirms by checking off items.

Next Steps

Now that you have a spec outlined, continue on to clarify the contens of the spec and answer any lingering questions the Agent has about what you’re trying to build.

Clarify