Git Strategy
Enterprise Workflow for Multi-Member Teams.
The Branching Model
main
------------------------------------[Production Stable]
feature/ABC-123
--------------------[Feature Release Branch]
story/ABC-123-ui
----[Developer Branch]
story/ABC-123-logic
-[Developer Branch]
The Committer Lifecycle
1. Discovery
TPO commits Spec
Functional requirements committed to the
specs/ directory./speckit.sf.specify
2. Validation
Arch commits Plan
Technical blueprint and drift audit results added to the feature folder.
/speckit.sf.plan
3. Scaffolding
Lead Dev commits Story 00
Mother Story creates the "Shell" (Metadata + Method Headers) to unblock the team.
/speckit.sf.implement
4. Parallel Dev
Devs commit Story PRs
Individual story branches are built and PR'd into the feature branch with evidence.
/speckit.sf.verify
hub
The "Mother Story" (Story 00)
Critical for multi-member teams. The Mother Story defines the contract between developers before logic is written.
- check_circle Metadata Layer: Deployment of Objects, Fields, and Permissions.
- check_circle Contract Layer: Class headers and empty LWC skeletons.
- check_circle Dependency Check: Ensures all story branches can compile immediately.
// Story 00: The Mother Story Scaffolding
implement(00-scaffold-shell) {
deploy_metadata([Objects, Fields, PS]);
create_class_headers(["Service", "Selector"]);
mark_complete_unblock_team();
}
Who Does What?
| Role | Responsibility | Key Command |
|---|---|---|
| Developer | Atomic implementation & Verification. | /speckit.sf.implement |
| Architect | Technical Blueprint & Promotion Logic. | /speckit.sf.deploy |
| QA / TPO | BPO Sign-off & Regression Testing. | /speckit.sf.qa |