// Surface Forge plugin documentation when users ask "how does forge work", "forge help", "what commands are available", or need guidance on workflows, commands, or concepts. Use for onboarding, command reference, or workflow overview questions.
Create and manage Flox development environments. Use when setting up a project environment during /forge:init, when a user asks to add a Flox environment, or when detecting and installing project dependencies. Covers flox init, search, install, manifest basics, and language-specific patterns. For advanced topics (services, builds, CUDA, layering, containers), suggest the full flox plugin.
This skill should be used when "restructuring commits", "organizing PR history", "making commits reviewable", or planning how to split work into atomic commits. The intellectual foundation for /reviewable. Do not use for writing commit messages (see git workflow guideline).
This skill should be used when the user redirects, corrects, or refines agent output — "no, actually", "that's not right", "you missed something". Captures correction moments to improve Forge workflows over time. Always active during feature work; log corrections as they occur.
This skill should be used when the user asks "what is an effort", "effort phases", "how do efforts work", "effort vs slice", or needs to understand the effort lifecycle. Covers the five phases: initialize, story capture, requirements, slice identification, and slice spawning.
This skill should be used when a command needs the full implement-and-review cycle — spawning an implementation worker, running a code review gate, and making a post-review decision. Used by /forge:start-task and /implement. Do not use for review-only or implementation-only workflows.
This skill should be used when /forge:process-pr-discussions needs to orchestrate its three-phase pipeline — analyze unresolved threads, delegate changes to specialized agents, then resolve threads. Do not use outside the PR discussion processing command.
| name | forge-docs |
| description | Surface Forge plugin documentation when users ask "how does forge work", "forge help", "what commands are available", or need guidance on workflows, commands, or concepts. Use for onboarding, command reference, or workflow overview questions. |
Help users find relevant Forge documentation.
Read from ${CLAUDE_PLUGIN_ROOT}/../docs/:
| File | Contents |
|---|---|
getting-started.md | Installation and first steps |
workflow-overview.md | Effort/slice lifecycle |
command-reference.md | All commands with examples |
Identify what the user is asking about
getting-started.mdworkflow-overview.mdcommand-reference.mdRead the relevant doc file Use the Read tool on the appropriate file.
Present the relevant section concisely Quote the most useful passage. Don't dump the entire file.
Offer to run the appropriate command
End with a suggestion: "Would you like me to run
/forge:work new to start a new slice?"
| User asks about... | Doc to read |
|---|---|
| Installing Forge | getting-started.md |
| First steps / setup | getting-started.md |
| What is an effort | workflow-overview.md |
| What is a slice | workflow-overview.md |
| How slices and efforts relate | workflow-overview.md |
| Available commands | command-reference.md |
How to use /forge:work | command-reference.md |
| How to start a task | command-reference.md |
| How retro notes work | workflow-overview.md |
If the docs directory doesn't exist or the file is empty,
explain that Forge is set up but documentation hasn't been
initialized, and offer to run /forge:init to set up the
project including documentation.