Add example workflow documentation showing multi-skill usage
Summary
The project lacks practical, step-by-step examples showing how multiple skills work together to accomplish real development tasks. While SKILLS_GUIDE.md lists skill combinations and docs/WORKFLOW_COMMANDS.md covers project management commands, there are no concrete walkthroughs demonstrating skills in action.
Current State
- SKILLS_GUIDE.md - Lists skill combinations (e.g., "Feature Forge + Fullstack Guardian + Test Master") but no detailed examples
- docs/WORKFLOW_COMMANDS.md - Documents Jira/Confluence workflow commands, not skill usage
- No
examples/directory - No example workflow files exist
Proposed Solution
Create an examples/ directory with 3-5 workflow walkthroughs showing real-world scenarios.
Suggested Examples
| File | Scenario | Skills Demonstrated |
|---|---|---|
REST_API_FROM_SCRATCH.md |
Building a complete API | Feature Forge → API Designer → FastAPI/NestJS Expert → Test Master → DevOps Engineer |
DEBUGGING_PRODUCTION_ISSUE.md |
Investigating and fixing a bug | Debugging Wizard → Monitoring Expert → Framework Skill → Test Master |
ADDING_AUTHENTICATION.md |
Securing an existing app | Secure Code Guardian → Framework Skill → Test Master → Security Reviewer |
LEGACY_CODE_MODERNIZATION.md |
Migrating old codebase | Spec Miner → Legacy Modernizer → Architecture Designer → Framework Skills |
FULL_STACK_FEATURE.md |
End-to-end feature implementation | Feature Forge → Fullstack Guardian → React/Vue + NestJS/FastAPI → Playwright Expert |
Example Format
# Building a REST API from Scratch
> **Skills used:** Feature Forge, API Designer, FastAPI Expert, Test Master, DevOps Engineer
> **Estimated time:** 2-4 hours
> **Difficulty:** Intermediate
## Overview
This walkthrough demonstrates building a production-ready REST API for a task management system, showing how skills chain together.
---
## Step 1: Define Requirements with Feature Forge
**Invoke:** "Help me define requirements for a task management API"
**What Feature Forge provides:**
- User stories with acceptance criteria
- API endpoint specifications
- Data model requirements
**Output excerpt:**
```markdown
### User Stories
1. As a user, I can create tasks with title, description, and due date
2. As a user, I can mark tasks as complete
...Step 2: Design the API with API Designer
Invoke: "Design RESTful endpoints for these task management requirements"
What API Designer provides:
- Resource modeling (proper REST conventions)
- OpenAPI specification
- Error handling patterns
Output excerpt:
paths:
/tasks:
get:
summary: List all tasks
parameters:
- name: status
in: query
schema:
type: string
enum: [pending, completed]
...Step 3: Implement with FastAPI Expert
Invoke: "Implement these endpoints using FastAPI with async SQLAlchemy"
What FastAPI Expert provides:
- Pydantic models with validation
- Async database operations
- Proper dependency injection
Output excerpt:
@router.get("/tasks", response_model=list[TaskResponse])
async def list_tasks(
status: TaskStatus | None = None,
db: AsyncSession = Depends(get_db)
) -> list[TaskResponse]:
...[Continue for remaining steps...]
Key Takeaways
- Skills build on each other - Feature Forge output feeds API Designer, which feeds implementation
- Each skill adds expertise - API Designer ensures REST best practices, FastAPI Expert ensures Python/async best practices
- Quality gates matter - Test Master and Security Reviewer catch issues before deployment
## Directory Structure
examples/ ├── README.md # Index of all examples ├── REST_API_FROM_SCRATCH.md ├── DEBUGGING_PRODUCTION_ISSUE.md ├── ADDING_AUTHENTICATION.md └── FULL_STACK_FEATURE.md
## Acceptance Criteria
- [ ] Create `examples/` directory
- [ ] Add `examples/README.md` with index and navigation
- [ ] Create at least 3 workflow examples (choose from suggested list)
- [ ] Each example shows 3+ skills working together
- [ ] Each example includes realistic code excerpts
- [ ] Examples reference actual skills by name
- [ ] Link examples from main README.md
## Why This Helps
1. **Reduces learning curve** - New users see skills in context, not isolation
2. **Demonstrates value** - Shows the multiplicative effect of skill combinations
3. **Provides templates** - Users can adapt workflows to their own projects
4. **Complements existing docs** - SKILLS_GUIDE.md says "what," examples show "how"Source: Jeffallan/claude-skills