The gsd-* family is the heaviest workflow option in the team’s toolbox — for projects that genuinely span weeks or months, not one sitting.
What you get: a persistent .planning/ folder with roadmap, milestones, per-phase artefacts (discuss / spec / plan / execute / verify / secure), and an audit trail. Pick it up next week and Claude remembers exactly where you left off.
When it’s right:
- Long horizon (weeks/months)
- Multiple collaborators
- Traceability matters
- You’ll pause and resume
When it’s overkill: one-off scripts, single-sitting prototypes — use plain or /team instead.
Common entry points: /gsd:new-project, /gsd:plan-phase, /gsd:execute-phase, /gsd:progress, /gsd:help. See /hub-glossary gsd for the broader framework explanation.
Access
Public — no access request needed. The canonical upstream is gsd-build/get-shit-done by TÂCHES.