solo-plan

# /plan This skill is self-contained — follow the steps below instead of delegating to external planning skills (superpowers, etc.). Research the codebase and create a spec + phased implementation plan. Zero interactive questions — explores the code instead. ## When to use Creates a track for any feature, bug fix, or refactor with a concrete, file-level implementation plan. Works with or without `/setup`. ## MCP Tools (use if available) - `session_search(query)` — find similar past work in Claude Code chat history - `project_code_search(query, project)` — find reusable code across projects - `codegraph_query(query)` — check dependencies of affected files - `codegraph_explain(project)` — architecture overview: stack, languages, directory layers, key patterns, top dependencies, hub files - `kb_search(query)` — search knowledge base for relevant methodology If MCP tools are not available, fall back to Glob + Grep + Read. ## Steps 1. **Parse task description** from `$ARGUMENTS`. - If empty, ask via AskUserQuestion: "What feature, bug, or refactor do you want to plan?" - This is the ONE question maximum. 2. **Detect context** — determine where plan files should be stored: **Project context** (normal project with code): - Detected by: `package.json`, `pyproject.toml`, `Cargo.toml`, `*.xcodeproj`, or `build.gradle.kts` exists in working directory - Plan path: `docs/plan/{trackId}/` **Knowledge base context** (documentation-centric project): - Detecte...