planning-tools

Plugin planning-tools from marketplace fractional-cto in oborchers/fractional-cto. Commands read from the repo's manifest — 18 days ago.

Skills (5)

• master-plan-methodology

  This skill should be used when authoring, reviewing, or modifying a multi-phase master planning document via the planning-tools plugin (especially the /plan-master and /plan-verify commands). Codifies the universal core sections, trigger-based optional sections, integer-only phase numbering, Open Qu

• plain-language

  This skill should be used whenever a planning-tools command prints something back to the user — the /plan-open-questions walkthrough, the /plan-master hand-off, the /plan-context scope report, the /plan-verify findings presentation, the /plan-progress chat summary, or any apply-gate summary. Single

• plan-verification-checklist

  This skill should be used by the plan-verifier agent and the /plan-verify command to audit a drafted master plan against a fixed checklist. Covers universal-core completeness, the v0.3.0+ no-tables-for-phases-or-questions rule, trigger-based section-coverage gaps, phase actionability (heading + per-

• progress-methodology

  This skill should be used when authoring or applying a progress update via the planning-tools plugin (the /planning-tools:plan-progress command). Codifies the dense-paragraph progress style, sub-markers (Piggybacked / Verification / Out of scope / Shipped), entry-key marker convention, SHA-tracking

• using-planning-tools

  This skill should be used when the user invokes any /plan-* command from the planning-tools plugin (/plan-context, /plan-master, /plan-open-questions, /plan-verify, /plan-tick, /plan-progress, /plan-delete), asks how Claude Code's plan files work, asks where plans are stored, asks to author or audit

Slash commands (7)

• /planning-tools:plan-context

  Pre-load context for a master plan — Triage picks domains autonomously, parallel Explore agents investigate, direct Reads verify findings. Emits a scope report. No plan file written.

• /planning-tools:plan-delete

  Clear the current session's plan file in ~/.claude/plans/ — delete, recreate empty, re-read to prime the next plan

• /planning-tools:plan-master

  Draft a multi-phase master planning document. Runs Triage + Parallel Explore + Verify (or reuses a /plan-context report), then dispatches plan-master-architect to synthesize. Writes to a project-local path.

• /planning-tools:plan-open-questions

  Walk through open questions one by one — from a master plan, a scope report, or questions already in the conversation. For each question, print a fixed short block (Why it matters / Where it matters), then capture the user's choice via a dedicated AskUserQuestion call per question (exactly one quest

• /planning-tools:plan-progress

  Synthesize a dense progress entry for the current branch and append/update it at the configured destination (markdown file, Linear ticket comment, or GitHub issue/PR comment). SHA-based idempotency means safe to re-run between phases.

• /planning-tools:plan-tick

  Auto-tick provenly-achieved phases of a master plan based on the current branch. /planning-tools:plan-tick (no args) audits and ticks all ACHIEVED phases. /planning-tools:plan-tick <phase> manually ticks one phase. No prompts.

• /planning-tools:plan-verify

  Audit a drafted master plan against the plan-verification-checklist. Dispatches the plan-verifier agent, presents findings, optionally appends a Verified marker on user approval.

Subagents (3)

• plan-context-worker

  Use this agent for parallel context discovery during master-plan creation. Each worker investigates one assigned domain (e.g., backend, frontend, analytics, research, ADRs) and returns well-cited findings with concrete path:line references (as its final message; best-effort persisted to a scratch fi

• plan-master-architect

  Use this agent to synthesize a multi-phase master planning document from a topic + worker findings. Runs after plan-context-worker agents have completed (or after a /plan-context report is passed via --context). Composes the universal core sections plus trigger-based optional sections, writes the pl

• plan-verifier

  Use this agent to audit a drafted master plan against the plan-verification-checklist. Runs after /plan-master writes a plan, and on demand via /plan-verify. Emits Critical/Important/Suggestion findings with file:line refs and a PASS/FAIL verdict — never modifies the plan itself. <example> Context:

Hooks (1)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

Similar plugins