SDD Lifecycle

The 15-Stage Journey from Constitution to Release.

The Step-by-Step Walkthrough

01

Constitution

Role: TPO

The "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
02

Specify

Role: TPO

Strategic 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
03

Clarify

Role: TPO + Arch

The 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
04

Plan

Role: Architect

Technical Architecture Blueprinting. The Architect generates the implementation strategy, defining exactly which classes, fields, and flows will be created.

/speckit.sf.plan
05

Stories

Role: Architect

Atomic Decomposition. The technical plan is broken down into self-contained story files in .specify/stories/ for easier execution.

/speckit.sf.stories
06

Review

Role: TPO + Arch

Human-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
07

Implement

Role: Developer

Autonomous 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]
08

Verify

Role: Developer

Quality Evidence. The Developer generates a formal verification report including code analyzer results and coverage heatmaps.

/speckit.sf.verify
09

PR

Role: Developer

The Contribution Gate. Automated Pull Request preparation via GitHub CLI, aggregating implementation details and verification evidence.

/speckit.sf.pr
10

QA

Role: QA Engineer

Persona-Based Validation. The QA team executes multi-persona validation scripts, ensuring security matrices and FLS are enforced.

/speckit.sf.qa
11

UAT

Role: BPO

Business Value Sign-off. The Business Product Owner (BPO) verifies that the functional objective has been correctly achieved in staging.

/speckit.sf.uat
12

Regression

Role: QA Engineer

Platform Sanity. A full suite of regression tests is executed to ensure no breaking changes were introduced into existing features.

/speckit.sf.regression
13

Score

Role: Lead

Health Dashboard. Real-time project health metrics across all stories are visualized to determine if the feature is ready for release.

/speckit.sf.score
14

Deploy

Role: Arch / RM

Promotion Gateway. Evidence-based release promotion across the landscape (Dev -> QA -> UAT -> Prod).

/speckit.sf.deploy
15

Release Notes

Role: TPO

Final Delivery. Automatically aggregates story summaries and testing results into a business-ready Release Note.

/speckit.sf.release-notes

Detailed Repository Blueprint

// Extension-Native Project Structure
Your-SF-Project/
├── .specify/
│ ├── memory/
│ │ └── constitution.md [Persistent Project context]
│ └── stories/
│ └── 00X-logic.story [Transient building units]
├── specs/
│ └── 001-billing-feature/
│ ├── spec.md [Functional Specs]
│ ├── clarify.md [Drift Analysis]
│ └── plan.md [Technical Blueprint]
├── force-app/
│ └── main/default/
│ ├── classes/
│ ├── lwc/
│ └── objects/
└── README.md