Systematic feature planning workflow - use when starting complex features requiring structured approach
Breaks down complex features into structured plans with business specs, technical design, and numbered implementation tasks. Triggers when starting multi-component features that touch backend, frontend, and infrastructure.
/plugin marketplace add ashchupliak/dream-team/plugin install dream-team@dream-team-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Transform complex feature requests into structured, executable plans.
Define what we're building and why:
## Feature: [Name]
### Problem Statement
[What problem does this solve?]
### Success Criteria
- [ ] [Measurable outcome 1]
- [ ] [Measurable outcome 2]
### Scope
**In Scope**: [what's included]
**Out of Scope**: [what's NOT included]
### Constraints
- [Technical constraints]
- [Business constraints]
How we'll build it:
## Technical Design
### Approach
[High-level approach in 2-3 sentences]
### Components
1. [Component 1] - [responsibility]
2. [Component 2] - [responsibility]
### Data Model
[Tables/entities needed]
### API Design
[Endpoints with methods]
### Dependencies
[External services/libraries needed]
Numbered steps for execution:
## Implementation Tasks
### S001: [First task]
- Files: [files to create/modify]
- Acceptance: [how to verify]
### S002: [Second task]
- Files: [files to create/modify]
- Acceptance: [how to verify]
[Continue with S003, S004, etc.]
Save planning documents to: .claude/plans/[feature-name].md
User: "Add user notification preferences"
Response:
# Feature: User Notification Preferences
## Phase 1: Business Spec
### Problem
Users cannot control which notifications they receive, leading to notification fatigue.
### Success Criteria
- [ ] Users can toggle email notifications
- [ ] Users can toggle in-app notifications
- [ ] Preferences persist across sessions
### Scope
**In**: Email, in-app notification toggles
**Out**: SMS, push notifications (future phase)
## Phase 2: Technical Design
### Approach
Add notification_preferences table linked to users, expose via REST API, update notification service to check preferences.
### Components
1. NotificationPreference entity
2. PreferenceService
3. PreferenceController
4. UI Settings panel
### API
GET/PUT /api/v1/users/{id}/notification-preferences
## Phase 3: Tasks
### S001: Database migration
- Files: V026__notification_preferences.sql
- Acceptance: Table exists with correct schema
### S002: Backend implementation
- Files: NotificationPreference.kt, PreferenceService.kt, PreferenceController.kt
- Acceptance: API returns/updates preferences
### S003: Frontend UI
- Files: settings/notifications.tsx
- Acceptance: User can toggle preferences
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.