flox Forge Documentation
Help users find relevant Forge documentation.
When to Use
- User asks about Forge concepts or workflow
- User needs command reference or examples
- User is new and needs onboarding guidance
- User asks "what is a slice", "what is an effort", "how do I start", or similar overview questions
Documentation Sources
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 |
Behavior
Identify what the user is asking about
- Onboarding / getting started →
getting-started.md - Lifecycle, efforts, slices, workflow →
workflow-overview.md - Specific commands, syntax, examples →
command-reference.md
- Onboarding / getting started →
Read 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 newto start a new slice?"
Common Questions and Sources
| 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 |
Fallback
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.