plan-one-issuelisted

Produce a comprehensive, reviewable implementation plan for a single work-unit before any code is written. Reads the real code (not just locates it), weighs the alternatives, names the existing utilities to reuse, and lays out context, approach, the per-file changes, the key decisions, edge cases, verification, and risks, scaled to the work's complexity. Read-only; emits the plan plus predicted files and a preliminary doc classification. Use for "plan this issue", "draft a plan for FRA-123", "scope and plan this ticket before coding", "what's the approach for this work-unit". The planning stage of the ship-it orchestrator, and usable standalone on an issue or a described task. Not for implementing (use fix-one-issue), batch-shipping many issues (use ship-issues), review (review-and-address), or just listing issues.
pricklywiggles/fractally-claude-marketplace · ★ 1 · AI & Automation · score 65

Install: claude install-skill pricklywiggles/fractally-claude-marketplace

# plan-one-issue: a comprehensive, read-only plan for one work-unit Produce the plan a careful engineer would write before touching code: grounded in the real codebase, weighing the obvious alternatives, and spelling out the change, the decisions, the edge cases, and how it will be verified. The deliberate planning stage; it runs concurrently (one per work-unit) inside the orchestrator and standalone on its own. Read-only: no edits, no commits, no worktrees. ## 1. Resolve the work-unit - **Orchestrated**: you are given a work-unit (`id`, `title`, `desc`, `branch`, `base`, `url`). Reason read-only against `base` (or the current checkout); do NOT create a worktree. - **Standalone**: given an issue id, fetch its intent (the default source); given a described task, use the text directly. ## 2. Read config Load the resolved config via `${CLAUDE_PLUGIN_ROOT}/scripts/load-config.sh`; read keys with `jq`: - `houseRules` / `safety` (the plan must respect them, e.g. code-only verification, or a "read the framework doc first" rail), - `verify` (so the plan's verification section names the real checks), - `planning.depth` (`light` | `adaptive` | `full`; see step 4), - `docs.jobs` (their `name` + `appliesWhen`, to classify `docNeed`). ## 3. Explore deeply (read-only) This is what separates a real plan from a guess. Do not stop at locating files: 1. **Read the code the change will touch.** Open the relevant files and understand the actual symbols, signatures, types, and surrounding