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.specifyprompt/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.mdthat includes user stories + functional requirements (per the template).spec.mdis 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.mdcan 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.
Comments
i ran spec command to update an existing textarea input to be a rich text editor, and i’m going through the spec.md it generated, it writes stuff like this which i don’t think will break anything, but i wonder in the end how much “unnecessary” fluff will be contained in all the markdown files:
I think it’s because without that it will sometimes not do stuff :p. Like a dev, it wants to know why it’s doing things.
i ran out of premium tokens so now using free models and 4o is unable to run the scripts? switching to 4.1 fixed for me
4o failing to run the underlying bash script for all of the speckit shortcuts for me
for some reason, mine often gets stuck trying to change to the branch it already changed to. i can fix it by just interrupting the conversation and notifying it it’s already on the correct branch: