And it ran through 2 of my Claude Code (Pro) sessions before I could start any real work. It was really powerful and had really good techniques for ensuring that AI-Driven long work stays on track and well verified. However it had over 30 commands, agent roles and workflows. It also forced that every task would get automatically commited, while I prefer to create PRs from feature branches. I started distilling the best of it into a smaller solution that allows the same core workflow: Plan -> Execute -> Verify. All while reducing both input and output tokens used. Then I started including small nice to haves:
- Want to pause work in progress and resume later? /gsdd-pause will write down a checkpoint in a .md file. Resume next session with /gsdd-resume
- You can plan phases and tasks without needing to create milestones. Useful when working at different mid-sized topica like Jira tickets
- You can configure how your work is going to be delivered: Conventional commits for every task, feature branches, or also just direct commits to main And quite a lot of other small improvements to make sure that it stays small but powerful. One example is when planning: The main agent writes the plan. A subagent will check the plan and raise errors if the plan does not meet the quality bar, then it will automatically be fixed in a loop. The result is now https://github.com/PatrickSys/workspine . It has 14 workflows in total, works with Claude Code, OpenCode, Codex, Cursor, Gemini CLI - and any coding agent using agent skills. You can Plan with claude, execute with Codex and review with Claude again easily. I’d love to get feedback from those who work with GSD or tried it out submitted by /u/SensioSolar
Originally posted by u/SensioSolar on r/ClaudeCode
You must log in or # to comment.