Llmops-demo-ts plan-task

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.

install

source · Clone the upstream repo

git clone https://github.com/yu-iskw/llmops-demo-ts

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/yu-iskw/llmops-demo-ts "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/plan-task" ~/.claude/skills/yu-iskw-llmops-demo-ts-plan-task && rm -rf "$T"

manifest: .claude/skills/plan-task/SKILL.md

source content

Plan Task

Create a detailed implementation plan for the following task:

$ARGUMENTS

Planning Steps

Research the codebase to understand current state relevant to this task
Identify all affected packages (common, agents, backend, frontend)
Break down into ordered tasks with clear dependencies
Assign each task to an agent role (software-engineer, designer, qa, etc.)
Identify risks and architectural decisions needed

Output Format

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.