groundwork-help
Skill45 starsChanged 4 days agoMITView on GitHub
List all Groundwork skills with descriptions. Usage /groundwork:groundwork-help
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- build-unplannedSkill
- check-specs-alignmentSkill
- create-tasksSkill
- debugSkill
- design-architectureSkill
- design-it-twiceSkill
- design-productSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- finalize-taskSkill
- groundwork-checkSkill
- handoffSkill
- implement-taskSkill
- instrument-observabilitySkill
- just-do-itSkill
- just-do-it-swarmingSkill
- plan-taskSkill
- review-prSkill
- select-projectSkill
- setup-repoSkill
- shipSkill
- skillsSkill
- source-architecture-from-codeSkill
- source-product-specs-from-codeSkill
- source-ux-design-from-codeSkill
- split-architectureSkill
- split-specsSkill
- staged-rolloutSkill
- statuslineSkill
- swarm-debugSkill
- swarm-design-architectureSkill
- task-validation-loopSkill
- test-driven-developmentSkill
- understanding-feature-requestsSkill
- use-git-worktreeSkill
- using-groundworkSkill
- ux-designSkill
- validateSkill
- vertical-sliceSkill
- work-on-next-taskSkill
- work-onSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read the plugin manifest and scan directories:
- Very specific: line 19
Read ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json for overview
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Groundwork Help
Lists all available skills and agents provided by the Groundwork plugin. Every Groundwork
capability is a skill, invoked either as /groundwork:<name> or automatically by the model.
Workflow
Step 1: Gather Component Information
Read the plugin manifest and scan directories:
- Read
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.jsonfor overview - Scan
${CLAUDE_PLUGIN_ROOT}/skills/for available skills (each<name>/SKILL.md) - Scan
${CLAUDE_PLUGIN_ROOT}/agents/for available verification/research agents
Step 2: Extract Descriptions
For each skill, extract the name and description from the SKILL.md YAML frontmatter. Note its
invocation tier from the frontmatter:
disable-model-invocation: true→ user-only slash workflowuser-invocable: false→ hidden library skill (model/other-skill use only)- neither → dual (user slash + model auto)
Step 3: Group and Present
Present the skills grouped by purpose. Hide user-invocable: false library skills from the
user-facing list (they are internal). Example grouping:
User-invocable skills (/groundwork:<name>)
List skills organized by purpose:
Spec-Driven Development:
/groundwork:design-product- Define product requirements/groundwork:design-architecture- Design technical approach/groundwork:create-tasks- Generate implementation tasks
Task Execution:
/groundwork:work-on [N]- Work on a specific task by number/groundwork:work-on-next-task- Work on the next task/groundwork:plan-task [N or description]- Plan a task or feature without implementing/groundwork:implement-task [N or plan-path]- Implement a previously planned task/groundwork:validate- Validate and autonomously fix the task worktree/groundwork:finalize-task [N]- Commit, merge, and clean up a validated task worktree
Quick Development:
/groundwork:build-unplanned [description]- Build a feature from description with worktree isolation and TDD
Sync & Alignment:
/groundwork:source-product-specs-from-code- Sync specs with code changes/groundwork:source-architecture-from-code- Update architecture docs/groundwork:check-specs-alignment- Verify spec alignment (full audit)/groundwork:split-specs- Convert single-file PRD into directory format/groundwork:split-architecture- Convert single-file architecture doc into directory format
Plugin Management:
/groundwork:groundwork-check- Validate plugin health/groundwork:groundwork-help- Show this help/groundwork:skills- List available skills
Debugging:
/groundwork:debug [description]- Systematic root-cause debugging/groundwork:swarm-debug [description]- Parallel adversarial hypothesis investigation
Design & UX:
/groundwork:ux-design- Establish a design system
Hidden library skills
Some skills (e.g. test-driven-development, understanding-feature-requests,
use-git-worktree, using-groundwork, task-validation-loop) are user-invocable: false:
they are not on the slash menu and are invoked only by other skills or by the model. Use
/groundwork:skills to see the full list of skills.
Step 4: Usage Examples
Provide usage examples:
/groundwork:design-product # Start defining a new product
/groundwork:design-architecture # Design the technical approach
/groundwork:create-tasks # Generate implementation tasks
/groundwork:work-on-next-task # Work on the next task
/groundwork:groundwork-check # Check plugin healthStep 5: Additional Resources
Point users to:
README.mdin the plugin root for full documentation- GitHub issues for support
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.

