Prioritizes tasks based on dependencies, business value, resource availability, and project goals. Use when you need to determine task execution order or prioritize work. Considers dependencies, value, urgency, and resource constraints.
/plugin marketplace add lexicalninja/secret-agents/plugin install lexicalninja-my-little-scrum-team@lexicalninja/secret-agentsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
## Task Prioritization
### Priority Groups
#### P0 - Critical (Do First)
- TASK-001: [description] - [rationale]
- TASK-002: [description] - [rationale]
#### P1 - High (Do Soon)
- TASK-003: [description] - [rationale]
- TASK-004: [description] - [rationale]
#### P2 - Medium (Normal Priority)
- TASK-005: [description] - [rationale]
#### P3 - Low (Can Defer)
- TASK-006: [description] - [rationale]
### Execution Order
1. [Phase]: [tasks]
2. [Phase]: [tasks]
### Critical Path
[Tasks that must be done sequentially]
### Parallel Opportunities
[Tasks that can run in parallel]
### Rationale
[Overall prioritization rationale]
Input: Prioritize tasks with dependencies
Output:
## Task Prioritization
### Priority Groups
#### P0 - Critical (Do First)
- TASK-001: Create specification - Blocks all other work
- TASK-002: Set up database schema - Blocks implementation tasks
- TASK-003: Break specification into tasks - Required before design/implementation
#### P1 - High (Do Soon)
- TASK-004: Design user interface - Blocks frontend implementation
- TASK-005: Design API structure - Blocks backend implementation
#### P2 - Medium (Normal Priority)
- TASK-006: Implement backend API - Depends on TASK-005
- TASK-007: Implement frontend - Depends on TASK-004
#### P3 - Low (Can Defer)
- TASK-008: Add documentation - Can be done after implementation
- TASK-009: Performance optimization - Can be deferred
### Execution Order
1. **Phase 1 (Sequential)**:
- TASK-001: Create specification
- TASK-003: Break into tasks
- TASK-002: Set up database
2. **Phase 2 (Parallel)**:
- TASK-004: Design UI
- TASK-005: Design API
3. **Phase 3 (Parallel)**:
- TASK-006: Implement backend
- TASK-007: Implement frontend
4. **Phase 4**:
- TASK-008: Documentation
- TASK-009: Optimization
### Critical Path
TASK-001 → TASK-003 → TASK-002 → TASK-005 → TASK-006
### Parallel Opportunities
- Phase 2: TASK-004 and TASK-005 can run in parallel
- Phase 3: TASK-006 and TASK-007 can run in parallel
### Rationale
Prioritization is primarily dependency-based. Foundation tasks (specification, database) must come first. Design tasks can run in parallel, then implementation. Documentation and optimization can be deferred.
Input: Prioritize tasks by business value
Output:
## Task Prioritization
### Priority Groups
#### P0 - Critical (Do First)
- TASK-001: User authentication - Critical for security and user access
- TASK-002: Core feature implementation - Primary business value
#### P1 - High (Do Soon)
- TASK-003: User dashboard - High user value
- TASK-004: Payment integration - Revenue impact
#### P2 - Medium (Normal Priority)
- TASK-005: User profile page - Standard feature
- TASK-006: Email notifications - Important but not critical
#### P3 - Low (Can Defer)
- TASK-007: UI polish - Nice-to-have
- TASK-008: Advanced search - Can be added later
### Execution Order
1. **Phase 1**: Core functionality
- TASK-001: Authentication
- TASK-002: Core feature
2. **Phase 2**: High-value features
- TASK-003: Dashboard
- TASK-004: Payments
3. **Phase 3**: Standard features
- TASK-005: Profile
- TASK-006: Notifications
4. **Phase 4**: Polish and enhancements
- TASK-007: UI polish
- TASK-008: Advanced search
### Critical Path
TASK-001 → TASK-002 → TASK-003
### Parallel Opportunities
- TASK-005 and TASK-006 can run in parallel
- TASK-007 and TASK-008 can run in parallel
### Rationale
Prioritization is value-based. Critical security and core features come first, followed by high-value user features. Standard features and polish can be done later.
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.