// Create a structured implementation plan for a feature, refactoring, or multi-step task. Use as the first step in the pipeline before /orchestrate. Produces a plan that the orchestrator can turn into a delegation plan.
Bump or upgrade declared dependency versions in this pnpm workspace (root and packages/* package.json), with supply-chain checks before and after install. Use when the user asks to upgrade, bump, or refresh npm dependencies in manifests—not only the lockfile.
Check license compatibility, data privacy compliance, and AI ethics. Use when adding dependencies, handling user data, or reviewing regulatory requirements.
Deploy the application or manage infrastructure. Handles Docker builds, CI/CD, and deployment workflows.
Design a UI component with specifications for layout, states, interactions, and accessibility. Use when creating new Vue.js components or redesigning existing ones.
Implement a feature or fix a bug following the project's TypeScript patterns and conventions. Use when code changes are needed.
Review code changes for quality, security, and adherence to project conventions. Use after making code changes or when reviewing a pull request.
| name | plan-task |
| description | Create a structured implementation plan for a feature, refactoring, or multi-step task. Use as the first step in the pipeline before /orchestrate. Produces a plan that the orchestrator can turn into a delegation plan. |
| argument-hint | [task description] |
| context | fork |
| agent | planner |
Create a detailed implementation plan for the following task:
$ARGUMENTS
Produce a structured plan in exactly this format:
## Task Plan
### Overview
[One paragraph summarizing the goal]
### Tasks
1. **[Task title]**
- Description: [What needs to be done]
- Package/files: [Which files will change]
- Dependencies: [Which task numbers must complete first, or "none"]
- Complexity: [Low / Medium / High]
- Agent: [software-engineer / designer / qa / code-reviewer / security / sre-devops / legal-compliance]
2. **[Task title]**
- Description: ...
- Package/files: ...
- Dependencies: ...
- Complexity: ...
- Agent: ...
### Risks & Considerations
- [Breaking changes, migration needs, test gaps, performance]
### Architecture Decisions
- [Design choices that need to be made upfront]
Be specific about file paths and concrete changes needed. This output will be fed to /orchestrate to create a parallel execution plan.