Get Stuff Done (gsd)

To turn a software idea into a shippable build plan with requirements traceability, this workflow extracts your SPEC, assigns REQ-IDs, generates a dependency-ordered ROADMAP, and executes phase-by-phase plan, execute, and verify artifacts. It persists everything in a .planning directory.

Requirements traceability in software planning maps every REQ-ID to exactly one phase with success criteria. It verifies code implementation through goal-backward checks to ensure artifacts exist and are wired correctly before marking the phase complete.

You maintain persistent build artifacts and context across CLI workflow sessions by writing phase context, plans, summaries, and verification files into a deterministic .planning/builds directory. This ensures your progress survives context clearing.

Yes, you can use agentic execution for autonomous software builds on existing brownfield projects by running the workflow with the --auto flag. It applies the same SPEC extraction, roadmapping, and verification processes to both new and existing codebases.

You need a spike or sketch to lock design direction before implementation when your feature idea has gray-area decisions. The workflow handles optional spike and sketch exploration to resolve design ambiguity before generating executable task plans.