spec-kit-sf (SFSpeckit)

Enterprise Salesforce Spec-Driven Development (SDD) Framework for GitHub Spec-Kit: AI-Powered, Human-in-the-Loop Engineering.

🚀 Official Community Announcement

SFSpeckit is the first-ever Salesforce extension officially accepted into the GitHub Spec Kit Community Catalog—the industry-leading SDD engine maintained by GitHub with over 141,000+ stars. Now proudly maintained and contributed to open source by Evernorth.

SFSpeckit transforms Salesforce delivery into an evidence-based, autonomous engine driven by structured specifications.

---

🌟 Featured at Dreamforce 2026 🚀

SFSpeckit was featured in Salesforce's Dreamforce 2026 session, "Explore the Agentic App Dev Roadmap," as an open-source GitHub Spec-Kit plugin tailored for Salesforce development.

The session covered Salesforce's evolving approach to agentic application development, including Spec-Driven Development and AI-assisted developer workflows.

🎥 Watch the Dreamforce 2026 session on Salesforce+

• Session: Explore the Agentic App Dev Roadmap
• Dreamforce: 2026
• Speakers: Dan Fernandez, VP, Product, Developer Services, Salesforce; Karishma Lalwani, Vice President, Product Management, Salesforce

---

🏗️ Spec-Driven Development (SDD) for AI

SFSpeckit is built on the philosophy of Spec-Driven Development (SDD). In the era of AI-agentic coding, jumping directly into implementation is the fastest way to hit context limits, create hallucinations, and accumulate technical debt.

The SDD Strategy:

Requirements (Spec) >>> Design (Plan) >>> Implementation (Build) >>> Test >>> Deploy

Important

Human-in-the-Loop (HITL) Engineering: SFSpeckit is a Spec-Driven Development framework that enforces human validation and verification at every milestone. This ensures that the AI remains a grounded co-pilot, eliminating hallucinations and context drift through rigorous human sign-offs.

The Tactical Lifecycle

graph TD
    subgraph Spec ["1. SPEC (Define What)"]
        C["/speckit.sf.constitution"] --> S["/speckit.sf.specify"]
        S --> CL["/speckit.sf.clarify"]
    end
    subgraph Plan ["2. PLAN (Define How)"]
        P["/speckit.sf.plan"] --> ST["/speckit.sf.stories"]
    end
    subgraph Build ["3. BUILD (Execute)"]
        I["/speckit.sf.implement"] --> V["/speckit.sf.verify"]
        V --> PR["/speckit.sf.pr"]
    end
    subgraph Test ["4. TEST (Validate)"]
        QA["/speckit.sf.qa"] --> U["/speckit.sf.uat"]
        U --> R["/speckit.sf.regression"]
        R --> SC["/speckit.sf.score"]
    end
    subgraph Deploy ["5. DEPLOY (Promote)"]
        D["/speckit.sf.deploy"]
    end
    Spec --> Plan --> Build --> Test --> Deploy

Loading

💡 The SDD Advantage

Capability	Raw AI Chat / Prompting	SFSpeckit SDD Engine
Context Management	Lost in chat history (Context Drift)	Grounded in central .specify/ specifications
Error Correction	Manual copy-pasting of error traces	Autonomous CLI Auto-Healing test loop
Code Governance	Inconsistent coding styles & hallucinations	Enforced 555-point rubric & Constitution
Team Scalability	Single-developer silo	Parallel multi-developer execution via Story 00

📜 The 9 Architectural Guardrails (Constitution)

When /speckit.sf.constitution runs, it establishes 9 enterprise articles that govern all downstream AI generations:

1. Metadata-First: Schema and fields must exist before business logic is generated.
2. Bulk-Awareness: Every Apex method must process 201+ records by default without hitting governor limits.
3. Declarative-First: Flow is prioritized for standard automations; Apex is reserved for complex processing.
4. Absolute Security: Strict enforcement of with sharing, FLS striping, and CRUD checks.
5. PNB Unit Testing: Positive, Negative, and Boundary (PNB) test cases are required for every story.
6. Separation of Concerns: Strict architectural layering (Triggers → Handlers → Services → Selectors).
7. Deployment Safety: Zero org-drift tolerance; validation deployments required prior to merge.
8. Platform Context: Explicit governor-limit profiling across asynchronous and synchronous boundaries.
9. Modular Logic: Single-responsibility, reusable Apex classes and isolated LWC components.

---

👥 SDD Workflow & Role Matrix

SFSpeckit structures the Salesforce delivery lifecycle into 5 distinct phases with clear human-in-the-loop accountability across 15 automated commands:

Phase	Stage	Command	Accountable Role	Purpose & Milestone Gate
1. Spec	01. Constitution	/speckit.sf.constitution	Architect / TPO	North Star: Project guardrails, governor limits & metadata conventions
	02. Specify	/speckit.sf.specify	Technical Product Owner (TPO)	Functional requirements engineering (What the business needs)
	03. Clarify	/speckit.sf.clarify	TPO + Architect	Reality check: Live org drift detection & requirement gap analysis
2. Plan	04. Plan	/speckit.sf.plan	Salesforce Architect	Technical blueprinting, class/flow mapping & blast radius analysis
	05. Stories	/speckit.sf.stories	Salesforce Architect	Atomic decomposition into self-contained .story units
	06. Review	/speckit.sf.review	TPO + Architect	HITL gate: Human sign-off on architecture before any code is built
3. Build	07. Implement	/speckit.sf.implement	Developer	Autonomous building with auto-healing test loop
	08. Verify	/speckit.sf.verify	Developer	Formal evidence generation, PMD/DFA static analysis & test coverage
	09. PR	/speckit.sf.pr	Developer	Automated Pull Request creation with embedded verification evidence
4. Test	10. QA	/speckit.sf.qa	QA Engineer	Multi-persona validation, security matrices & FLS enforcement
	11. UAT	/speckit.sf.uat	Business Product Owner (BPO)	Business value verification & user acceptance sign-off in sandbox
	12. Regression	/speckit.sf.regression	QA Engineer	Platform sanity & cross-story regression test execution
	13. Score	/speckit.sf.score	Lead / Architect	555-point quality dashboard evaluation across all stories
5. Deploy	14. Deploy	/speckit.sf.deploy	Architect / Release Manager	Multi-environment promotion gateway (Dev → QA → UAT → Prod)
	15. Release Notes	/speckit.sf.release-notes	TPO	Automated generation of business-ready release documentation

Tip

The Story 00 Scaffolding Pattern: For multi-developer teams, /speckit.sf.stories automatically generates 00-shell.md as the initial scaffolding story (Story 00). It deploys foundational metadata (Objects, Fields, PermSets) and compiles skeleton class headers/interfaces first. This establishes an immutable architectural contract, allowing multiple developers to build their implementation stories in parallel without compilation blockers.

Role Accountability Summary

• Technical Product Owner (TPO): Governs business intent, approves architectural plans, validates UAT, and issues release notes.
• Salesforce Architect: Enforces constitution guardrails, authors blueprints & blast radius maps, and oversees production promotions.
• Developer: Executes story implementation with autonomous self-healing loops and produces verification evidence.
• QA Engineer: Validates security matrices across profiles/permission sets and manages regression test suites.
• Business Product Owner (BPO): Validates functional business criteria before deployment.
• Release Manager (RM) / Lead: Audits quality scores and coordinates cross-environment release pipelines.

---

⚡ Prerequisites

Requirement	Minimum Version	Required?	Purpose
Node.js	≥ 18.0.0	✅ Yes	Required runtime for developer tooling and LWC Jest tests.
Salesforce CLI (sf)	≥ 2.0.0	✅ Yes	Core engine for all Salesforce metadata and deployments.
SF Code Analyzer	≥ 5.0.0	✅ Yes	Static analysis (PMD 7) and data-flow analysis (DFA).
GitHub CLI (gh)	≥ 2.0.0	⚠️ Optional	Automated Pull Request creation, checks, and release management.
DX Project	—	✅ Yes	Project must be an initialized Salesforce DX project (sfdx-project.json).

---

🚀 Installation & Setup

Step 1: Install Spec Kit CLI

You must have the core Spec Kit toolkit installed before adding SFSpeckit:

# Install Spec Kit via uv (Official Recommended Method)
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

Step 2: Add SFSpeckit Extension

Once Spec Kit is installed, you can add SFSpeckit directly:

# Add SFSpeckit to your active Salesforce project
specify extension add sf --from https://github.com/Evernorth/spec-kit-sf

For specific releases:

specify extension add sf --from https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip

Step 3: Automated Environment Setup & Verification

After adding the extension, run the automated setup command inside your Salesforce DX project. SFSpeckit will detect your OS, inspect your local environment, and verify (or prompt to install) all required tooling:

/speckit.sf.setup

Environment Verification Checklist

The /speckit.sf.setup command automatically inspects and validates:

1. Salesforce CLI (sf): Minimum version 2.0.0 — Core engine for Salesforce metadata retrieval, deployments, and org operations.
2. Salesforce Code Analyzer (@salesforce/plugin-code-analyzer): Version 5.x — PMD 7 and Graph Engine (DFA) static analysis rules.
3. GitHub CLI (gh): Minimum version 2.0.0 (Optional) — Automated pull request creation, checks, and release management.

---

📋 Slash Commands (19 Complete Lifecycle Tools)

Command	Persona	Purpose
/speckit.sf.setup	Dev/Arch	[SETUP] Automated dependency checker and installer (sf, gh, code-analyzer).
/speckit.sf.constitution	TPO	[DISCOVERY] Establish project principles with 9 articles and org discovery.
/speckit.sf.specify	TPO	Create functional feature specs with object maps and security models.
/speckit.sf.clarify	Arch	[DRIFT ALERT] Deep gap analysis checklist and drift audit.
/speckit.sf.plan	Arch	Technical blueprint, force-app structure, and blast radius analysis.
/speckit.sf.stories	Arch	Break plan into Jira-ready developer stories with security matrices.
/speckit.sf.analyze	Dev	[PRE-FLIGHT] Pre-implementation analysis with Story 00 context and org drift detection.
/speckit.sf.implement	Dev	[AUTO-HEAL] Build story with automated remediation loops (up to 3 retries).
/speckit.sf.review	TPO/Arch	TPO and Architect review of generated stories before Jira creation.
/speckit.sf.verify	Dev	Generate formal Verification Evidence documents with coverage metrics.
/speckit.sf.pr	Dev	Prepare PR with scoring gates and code review checklist via gh.
/speckit.sf.qa	QA	Multi-persona UI validation, Jest tests, and Apex test execution.
/speckit.sf.uat	BPO	Generate UAT scripts and manage business sign-offs.
/speckit.sf.score	QA/Arch	555-point real-time quality scoring dashboard across Metadata, Apex, and LWC.
/speckit.sf.deploy	Arch	Multi-org promotion logic (Dev $\rightarrow$ QA $\rightarrow$ UAT $\rightarrow$ Prod).
/speckit.sf.change	TPO	Handle mid-sprint requirement changes with impact analysis.
/speckit.sf.hotfix	Dev	Emergency production patch workflow with fast-track deployment.
/speckit.sf.regression	QA	Full feature regression tests across all stories before release.
/speckit.sf.release-notes	TPO	Auto-generate release notes from completed stories and test results.

---

📁 Repository Structure

SFSpeckit organizes all SDD artifacts inside the .specify directory to maintain a clean project root:

.specify/
├── memory/
│   └── constitution.md                 # Project "North Star" principles
├── specs/                              # Feature Specifications
│   └── 001-feature-name/
│       ├── spec.md                     # Functional Spec
│       ├── plan.md                     # Technical Blueprint & Blast Radius
│       ├── verification-evidence.md    # Automated Evidence & Test Metrics
│       └── stories/                    # Developer Work Units
│           ├── 00-shell.md             # Story 00 (Metadata & Skeletons)
│           └── 01-logic.md             # Implementation Story
├── extensions/
│   └── sf/                             # Extension Config
│       └── sf-config.yml
force-app/                              # Salesforce Metadata Source
sfdx-project.json                       # Core Salesforce DX Configuration

---

🤝 Community & Governance

• Contributing: Please review our Contributing Guidelines and Code of Conduct.
• Changelog: All notable releases are documented in CHANGELOG.md.

---

👥 Original Contributors

• Sumanth Yanamala (LinkedIn), Salesforce Architect, Evernorth

This framework is a contribution to the global Salesforce community. SFSpeckit is shared as a way to give back to the ecosystem.

---

⚖️ License

SFSpeckit is Open Source software released under the Apache 2.0 license.