gsd-capture
Skill1 starsChanged 31 days agoMITView on GitHub
Capture ideas, tasks, notes, and seeds to their destination
4 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- open-gsd/get-shit-done-reduxedited, first seen Oct 8, 2026
- adrianoanthonymma16-boop/opencode-agentsedited, first seen Sep 16, 2026
- open-gsd/gsd-coreedited, first seen Sep 2, 2026
- ZaneL1u/cloud-cli-proxyedited, first seen May 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- open-gsd/get-shit-done-redux★ 11k57% same
- open-gsd/gsd-core★ 11k57% same
- ZaneL1u/cloud-cli-proxy★ 5753% same
- adrianoanthonymma16-boop/opencode-agents★ 172% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- analysis-documentationSkill
- browser-automationSkill
- business-metrics-calculatorSkill
- chat-attachment-is-not-a-fileSkill
- claude-code-masterySkill
- codebase-designSkill
- codex-cli-specialistSkill
- cohort-analysisSkill
- cut-the-curveSkill
- data-narrative-builderSkill
- data-quality-auditSkill
- domain-modelingSkill
- focused-fixSkill
- funnel-analysisSkill
- gate-must-derive-its-criterionSkill
- grill-with-docsSkill
- gsd-add-testsSkill
- gsd-ai-integration-phaseSkill
- gsd-audit-fixSkill
- gsd-audit-milestoneSkill
- gsd-audit-uatSkill
- gsd-autonomousSkill
- gsd-cleanupSkill
- gsd-code-reviewSkill
- gsd-complete-milestoneSkill
- gsd-configSkill
- gsd-debugSkill
- gsd-discuss-phaseSkill
- gsd-docs-updateSkill
- gsd-eval-reviewSkill
- gsd-execute-phaseSkill
- gsd-exploreSkill
- gsd-extract-learningsSkill
- gsd-fastSkill
- gsd-forensicsSkill
- gsd-graphifySkill
- gsd-healthSkill
- gsd-helpSkill
- gsd-importSkill
- gsd-inboxSkill
- gsd-ingest-docsSkill
- gsd-managerSkill
- gsd-map-codebaseSkill
- gsd-milestone-summarySkill
- gsd-mvp-phaseSkill
- gsd-new-milestoneSkill
- gsd-new-projectSkill
- gsd-ns-contextSkill
- gsd-ns-ideateSkill
- gsd-ns-manageSkill
- gsd-ns-projectSkill
- gsd-ns-reviewSkill
- gsd-ns-workflowSkill
- gsd-pause-workSkill
- gsd-phaseSkill
- gsd-plan-phaseSkill
- gsd-plan-review-convergenceSkill
- gsd-pr-branchSkill
- gsd-profile-userSkill
- gsd-progressSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 1 is common, 0 are distinctive, and 4 are very specific to this project.
1
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 23
--backlog: Add an idea to the backlog parking lot (999.x numbering) → add-backlog workflow
- Very specific: line 53
If it is --note: strip the flag, pass remainder to note workflow
- Very specific: line 54
If it is --backlog: strip the flag, pass remainder to add-backlog workflow
- Very specific: line 55
If it is --seed: strip the flag, pass remainder to plant-seed workflow
- Very specific: line 56
If it is --list: pass remainder (optional area filter) to check-todos workflow
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<objective>
Capture ideas, tasks, notes, and seeds to their appropriate destination in the GSD system.Mode routing:
- default (no flag): Capture as a structured todo for later work → add-todo workflow
- --note: Zero-friction idea capture (append/list/promote) → note workflow
- --backlog: Add an idea to the backlog parking lot (999.x numbering) → add-backlog workflow
- --seed: Capture a forward-looking idea with trigger conditions → plant-seed workflow
- --list: List pending todos and select one to work on → check-todos workflow
</objective>
<routing>| Flag | Destination | Workflow |
| (none) | Structured todo in .planning/todos/ | add-todo |
| --note | Timestamped note file, list, or promote | note |
| --backlog | ROADMAP.md backlog section (999.x) | add-backlog |
| --seed | .planning/seeds/SEED-NNN-slug.md | plant-seed |
| --list | Interactive todo browser + action router | check-todos |
</routing><execution_context> @$HOME/.claude/get-shit-done/workflows/add-todo.md @$HOME/.claude/get-shit-done/workflows/note.md @$HOME/.claude/get-shit-done/workflows/add-backlog.md @$HOME/.claude/get-shit-done/workflows/plant-seed.md @$HOME/.claude/get-shit-done/workflows/check-todos.md @$HOME/.claude/get-shit-done/references/ui-brand.md </execution_context>
<context>
Arguments: $ARGUMENTSParse the first token of $ARGUMENTS:
- If it is
--note: strip the flag, pass remainder to note workflow - If it is
--backlog: strip the flag, pass remainder to add-backlog workflow - If it is
--seed: strip the flag, pass remainder to plant-seed workflow - If it is
--list: pass remainder (optional area filter) to check-todos workflow - Otherwise: pass all of $ARGUMENTS to add-todo workflow
</context>
<process>
1. Parse the leading flag (if any) from $ARGUMENTS.
2. Load and execute the appropriate workflow end-to-end based on the routing table above.
3. Preserve all workflow gates from the target workflow (directory structure, duplicate detection, commits, etc.).
</process>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.