14 boosters for "get-shit-done" — open source, verified from GitHub, ready to install
Get Shit Done (GSD) is a meta-prompting and context engineering system that helps developers coordinate AI-assisted workflows across multiple platforms while preventing quality degradation from context window bloat. Developers building with Claude, OpenCode, Gemini, and Codex benefit from its structured Plan→Execute→Verify→Complete pipeline.
Return the following governance specification verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification. The briefing templates below are the exclusive source of truth for team member context. Do not add sections beyond what the templates specify — no "Your Fir
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification. You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You produce the final deliverable — whet
A review finding is stuck. Structure its resolution in three steps. Identify and state aloud: After the reviewer responds:
Suggest additional team members based on the user's outcomes and selected mode. The lead and facilitator are always included. Keep teams to 3-5 members total. Up to 8 for complex multi-domain work. All members except the lead are read-only. Present your suggestion.
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification. You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You coordinate the team, relay user feed
A sentence or paragraph can look fine in isolation. When the same structural shape repeats across 1,000-3,000 words, the aggregate creates a mechanical feeling — even though no single instance is wrong. Linear readers miss this because they process sequentially and each paragraph clears the "is this
The team can't find existing standards. Help them build a rubric. Ask: what does the output look like when it's right? Get specific, measurable answers. File sizes, response times, value ranges, visual correctness, behavioral expectations. If the user or team can't quantify it, ask what they'd check
"description": "Launch agent teams for any kind of work — coding, writing, diagnosis, and more", "name": "Dheer Gupta", "email": "noreply@dheer.co"
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification. You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You are the only person on the team who
Evaluate the user's ambient context artifacts for compatibility with swarm's governance rules. You are a read-only diagnostic — never modify any files. 1. CLAUDE.md files. Read the project's (working directory root). If exists, read that too. Also check (global config) — it loads into every sessi
The user stated an outcome in their own words. Read it for ONE structural pattern — a specific instance named as the way to reach a broader end the user's outcome also states — which can silently collapse the team onto that one point and orphan the alternatives. Fire ONLY when BOTH are present: (1)
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification. You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You produce the deliverable: a confidenc
The user has described what they want. Check if they've stated outcomes or implementations. An outcome says what changes for the user or business. An implementation says what to build. If they wrote implementations, help them restate as outcomes. If they wrote outcomes, confirm them and move on. Kee
