Git Strategy
Enterprise Workflow for Multi-Member Teams.
The Branching Model
main
------------------------------------[Production Stable]
feature/ABC-123
--------------------[UAT / Release Candidate]
story/ABC-123-ui
----[Dev Branch]
story/ABC-123-logic
-[Dev Branch]
The Committer Lifecycle
1. Discovery
TPO commits Spec
Initial functional requirements committed to the
main or draft branch./sfspeckit-specify
2. Validation
Arch/TPO commit Clarify
Gap analysis and drift detection results added to the feature spec folder.
/sfspeckit-clarify
3. Architecture
Arch commits Plan & Stories
The technical blueprint and story decomposition are committed to the feature branch.
/sfspeckit-plan
4. Scaffolding
Lead Dev commits Story 00
Mother Story creates the "Shell" (Metadata + Method Headers) to unblock the team.
/sfspeckit-implement
5. Parallel Dev
Devs commit Story PRs
Team members work on individual story branches and PR into the feature branch.
/sfspeckit-pr
hub
The "Mother Story" (Story 00)
Parallel development often stalls because developers are waiting for the underlying Schema or Apex headers. The **Mother Story** solves this by creating the shell first.
- check_circle Metadata Layer: Creates all Objects, Fields, and Relationships.
- check_circle Scaffold Layer: Creates Apex Class headers and LWC Skeletons (empty methods).
- check_circle Unblocker: Allows other devs to write logic immediately against a "mocked" interface.
// Story 00: The Scaffold Build
implement(00-feature-shell) {
create_objects([Billing_Config__c, ...]);
create_apex_header("BillingService", ["calculateTax", ...]);
create_lwc_skeleton("billingDashboard");
}
// Status: Team Unblocked
Who Does What?
| Role | Responsibility | Tool/Command |
|---|---|---|
| Developer | Build logic & generate evidence. | /sfspeckit-implement |
| Architect | Review code & guide architecture. | /sfspeckit-clarify |
| QA / TPO | Verify features & release notes. | /sfspeckit-qa |