@help - Skill Discovery
Help users find the right skill for their task.
Quick Reference
code
@help # List all skills @help "how to fix a bug" # Get skill recommendation @help workflow # Show workflow skills
Trigger
When user types:
- •
@help - •
@help "query" - •
@help what skill to use
Workflow
1. Understand Intent
What is the user trying to do?
- •New feature → Workflow skills
- •Bug fix → Fixes/Debugging skills
- •Deployment → Deployment skills
- •Not sure → Ask clarifying question
2. Match to Skill
Map intent to skill category:
code
User intent: ├── New feature → @feature (or @idea → @design → @build) ├── Fix bug │ ├── Production down (P0) → @hotfix │ ├── Quality issue (P1/P2) → @bugfix │ └── Needs triage → @issue ├── Debug problem → /debug ├── Execute workstream → @build ├── Deploy feature → @review → @deploy └── Not sure → Ask clarifying question
3. Provide Guidance
- •Show usage example
- •Explain when to use
- •Mention related skills
Example Interactions
Bug Fix Routing
User: @help "I found a bug in login"
Response:
Based on your description, here are your options:
- •
@issue - If you need to classify severity first
code@issue "Bug in login"- •
@bugfix - If it's a quality issue (not critical)
code@bugfix "Login bug description"- •
/debug - If you need to investigate the root cause
code/debug "Login fails under condition X"Which approach fits your situation?
New Feature
User: @help how to add a new feature
Response:
For new features, use @feature for the full workflow:
code@feature "Add user comments"This will:
- •Interview you about requirements (@idea)
- •Create workstream breakdown (@design)
- •Guide you through execution (@build)
Alternatively, you can use individual skills:
- •
@idea→ requirements gathering- •
@design→ workstream planning- •
@build→ execute one workstream
Output
Always provide:
- •Recommended skill with command
- •Brief explanation of why
- •Example usage
- •Related alternatives
See Also
- •Skill Registry - All skill definitions
- •SDP Skills Command - CLI implementation