---
name: plan
description: "Plan a task with engine-powered dependency analysis"
category: workflow
tags: [plan, task, dependency]
depends-on: [init]
input: "task description"
output: "structured plan with file targets and dependency graph"
token-estimate: 1500
parallel-safe: true
argument-hint: "[task description]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Bash, AskUserQuestion, EnterPlanMode
model: claude-opus-4-6
context: inline
agent: general-purpose
---

# Plan — Engine-Powered Task Planning

Plan the requested task. The engine provides the dependency graph and relevant files.

## Precise Context (auto-generated by engine)

!`ccs context "$ARGUMENTS" 2>/dev/null || node "$HOME/.claude/skills/_ccs/engine/cli.js" context "$ARGUMENTS" 2>/dev/null`

## Steps

### 1. Analyze the context
Using the engine output above:
- Identify all files that need modification
- Trace the dependency chain (which files import the targets)
- Check if tests exist for affected files

### 2. Create the plan
- **Files to read**: From the context above
- **Files to modify**: Where the changes go
- **Files to create**: New components/modules needed
- **Files affected downstream**: Importers that may need updates
- **Test strategy**: Which tests to run/create

### 3. Present to user
Output a clear, numbered implementation plan. Ask for confirmation.

## Rules
- Never start coding — plan only
- If the task is trivial (1-2 files), suggest `/ccs-build` directly
- After approval → suggest `/ccs-build` to execute

---
*codebase-context-skill v2.0.0*