plannerlisted

## Activation When this skill activates, IMMEDIATELY invoke the corresponding script. The script IS the workflow. | Mode | Intent | Entry point | | --------- | ---------------------------------- | ------------------------------------------- | | planning | "plan", "design", "architect" | `skills.planner.orchestrator.planner` step 1 | | execution | "execute", "implement", "run plan" | `skills.planner.orchestrator.executor` step 1 | Each command is self-contained -- the `--project` expression prefers a project-local install and falls back to the user-global one. Run one whole line; shell state does not persist between invocations. **planning** ```bash uv run --project "$(d="${CLAUDE_PROJECT_DIR:-$PWD}"; [ -d "$d/.claude/skills/scripts" ] && echo "$d/.claude/skills/scripts" || echo "$HOME/.claude/skills/scripts")" python -m skills.planner.orchestrator.planner --step 1 ``` **execution** ```bash uv run --project "$(d="${CLAUDE_PROJECT_DIR:-$PWD}"; [ -d "$d/.claude/skills/scripts" ] && echo "$d/.claude/skills/scripts" || echo "$HOME/.claude/skills/scripts")" python -m skills.planner.orchestrator.executor --step 1 ``` **Run these with the shell sitting inside the project.** The Bash working directory persists between calls, so it may still be in a sibling repo or a vendored checkout from earlier work -- check it, and `cd` into the project first if it is not already there. Do not `cd` into the skills direct