gsd-phase
Skill1 starsChanged 57 days agoMITView on GitHub
CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
4 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- sp1e/claude-skillsedited, first seen Oct 12, 2026
- open-gsd/get-shit-done-reduxedited, first seen Oct 8, 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★ 11k67% same
- open-gsd/gsd-core★ 11k67% same
- ZaneL1u/cloud-cli-proxy★ 5752% same
- sp1e/claude-skills★ 184% 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 repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-mattSkill
- banner-designSkill
- brandSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- designSkill
- design-systemSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- gsd-add-testsSkill
- gsd-ai-integration-phaseSkill
- gsd-audit-fixSkill
- gsd-audit-milestoneSkill
- gsd-audit-uatSkill
- gsd-autonomousSkill
- gsd-captureSkill
- 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-mempalace-captureSkill
- gsd-mempalace-recallSkill
- gsd-milestone-summarySkill
- gsd-mvp-phaseSkill
- gsd-new-milestoneSkill
- gsd-new-projectSkill
- gsd-nextSkill
- gsd-ns-contextSkill
- gsd-ns-ideateSkill
- gsd-ns-manageSkill
- gsd-ns-projectSkill
- gsd-ns-reviewSkill
- gsd-ns-workflowSkill
- gsd-onboardSkill
- gsd-pause-workSkill
- gsd-plan-phaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 12
--remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
- Very specific: line 38
If it is --insert: strip the flag, pass remainder (format: <after-phase-number> <description>) to insert-phase workflow
- Very specific: line 39
If it is --remove: strip the flag, pass remainder (phase number) to remove-phase workflow
- Very specific: line 40
If it is --edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase 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>
Manage phases in ROADMAP.md with a single consolidated command.Mode routing:
- default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
- --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
- --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
- --edit: Edit any field of an existing phase in place → edit-phase workflow
</objective>
<routing>| Flag | Action | Workflow |
| (none) | Add new integer phase at end of milestone | add-phase |
| --insert | Insert decimal phase (e.g., 72.1) after specified phase | insert-phase |
| --remove | Remove future phase, renumber subsequent | remove-phase |
| --edit | Edit fields of existing phase in place | edit-phase |
</routing><execution_context> @/home/tony/.config/opencode/gsd-core/workflows/add-phase.md @/home/tony/.config/opencode/gsd-core/workflows/insert-phase.md @/home/tony/.config/opencode/gsd-core/workflows/remove-phase.md @/home/tony/.config/opencode/gsd-core/workflows/edit-phase.md </execution_context>
<context>
Arguments: $ARGUMENTSParse the first token of $ARGUMENTS:
- If it is
--insert: strip the flag, pass remainder (format:<after-phase-number><description>) to insert-phase workflow - If it is
--remove: strip the flag, pass remainder (phase number) to remove-phase workflow - If it is
--edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow - Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow
Roadmap and state are resolved in-workflow via init phase-op and targeted reads.
</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 validation gates from the target workflow.
</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.