SDD Lifecycle
The 15-Stage Journey from Constitution to Release.
The Step-by-Step Walkthrough
Constitution
Role: TPOThe "North Star" for your project. Before any feature work begins, the TPO executes a project-wide scan to establish architectural guardrails. This locks metadata conventions into the .specify/memory/constitution.md file.
/speckit.sf.constitution
Specify
Role: TPOStrategic Requirement Engineering. The TPO writes a functional specification that defines WHAT the feature must do from a business perspective, located in the specs/ directory.
/speckit.sf.specify
Clarify
Role: TPO + ArchThe Reality Check. The Architect and TPO run a discovery cycle to see if the active Salesforce Org has any manual changes (Drift) that conflict with the specification.
/speckit.sf.clarify
Plan
Role: ArchitectTechnical Architecture Blueprinting. The Architect generates the implementation strategy, defining exactly which classes, fields, and flows will be created.
/speckit.sf.plan
Stories
Role: ArchitectAtomic Decomposition. The technical plan is broken down into self-contained story files in .specify/stories/ for easier execution.
/speckit.sf.stories
Review
Role: TPO + ArchHuman-in-the-Loop Validation. No automated code is written until a human confirms that the planned architecture perfectly serves the business intent.
/speckit.sf.review
Implement
Role: DeveloperAutonomous Building. The Developer executes the story files. SFSpeckit writes code, runs tests, fixes errors, and iterates until the technical plan is fulfilled.
/speckit.sf.implement [story]
Verify
Role: DeveloperQuality Evidence. The Developer generates a formal verification report including code analyzer results and coverage heatmaps.
/speckit.sf.verify
PR
Role: DeveloperThe Contribution Gate. Automated Pull Request preparation via GitHub CLI, aggregating implementation details and verification evidence.
/speckit.sf.pr
QA
Role: QA EngineerPersona-Based Validation. The QA team executes multi-persona validation scripts, ensuring security matrices and FLS are enforced.
/speckit.sf.qa
UAT
Role: BPOBusiness Value Sign-off. The Business Product Owner (BPO) verifies that the functional objective has been correctly achieved in staging.
/speckit.sf.uat
Regression
Role: QA EngineerPlatform Sanity. A full suite of regression tests is executed to ensure no breaking changes were introduced into existing features.
/speckit.sf.regression
Score
Role: LeadHealth Dashboard. Real-time project health metrics across all stories are visualized to determine if the feature is ready for release.
/speckit.sf.score
Deploy
Role: Arch / RMPromotion Gateway. Evidence-based release promotion across the landscape (Dev -> QA -> UAT -> Prod).
/speckit.sf.deploy
Release Notes
Role: TPOFinal Delivery. Automatically aggregates story summaries and testing results into a business-ready Release Note.
/speckit.sf.release-notes