create-planlisted

# Create Implementation Plan > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. !`python3 ${CLAUDE_PLUGIN_ROOT}/scripts/inject-rules.py engineering-judgment` Transform requirements into detailed, TDD-driven implementation plans via structured exploration and analysis. **Core Principle:** Explore → Design → Outline+Verify → Write **Optimize for parallel execution.** The plan is consumed by `/bdk:subagent-execute-plan`, which fans out as many implementer subagents as it can run concurrently. The single biggest lever on end-to-end speed is **how the plan decomposes work**: tasks that touch disjoint files and declare honest dependencies let the executor run a wide wave instead of a long serial chain. A plan that is correct but accidentally serial is a slow plan. Design the task graph to be **wide and shallow**, not deep. **Announce at start:** "Using create-plan to build an implementation plan." **Hard rules:** - Do NOT implement code — plan is the only deliverable. - Do NOT hardcode language tools (`pytest`, `npm`, `cargo`) — use injected values or fall back to "run the project's test suite". - Every task MUST declare its `Files:` and its `Depends on:` (or `Depends on: none`). The executor uses both to compute parallel waves — omitting them forces conservative serial fallback. --- ## Workflow ### Phase 1: Parse & Setup 1. **Validate input** - `$ARGUMENTS` empty/blank → ask user to describe feature, **stop**. - Vague