agentleFS
sp1esp1e/claude-skills/gsd-ns-workflow/SKILL.md

gsd-ns-workflow

Skill1 starsChanged 31 days agoMITView on GitHub

workflow | discuss plan execute verify phase progress

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Route to the appropriate phase-pipeline skill based on the user's intent. Sub-skill names below are post-#2790 consolidated targets — gsd-phase absorbs the former add/insert/remove/edit-phase commands and gsd-progress absorbs the former next/do commands.

User wantsInvoke
Gather context before planninggsd-discuss-phase
Clarify what a phase deliversgsd-spec-phase
Create a PLAN.mdgsd-plan-phase
Execute plans in a phasegsd-execute-phase
Verify built features through UATgsd-verify-work
Add / insert / remove / edit a phasegsd-phase
Advance to the next logical stepgsd-progress
Offload planning to the ultraplan cloudgsd-ultraplan-phase
Cross-AI plan review convergence loopgsd-plan-review-convergence

Invoke the matched skill directly using the Skill tool.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.