메뉴
Manage hierarchical planning documents with token-budgeted lazy loading, automatic rebalancing, and cascading context injection. Use when working with large planning docs, splitting oversized plans, or loading plan hierarchies into context efficiently.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate and serve rich HTML companions to markdown discovery documents: paired markdown→HTML rendering (marked + mermaid + data-driven cytoscape/plotly fenced blocks), a vendored draw.io stencil library (~AWS/GCP/Azure/K8s SVG icons) for composing custom architecture diagrams, an injectable design-tokens brandpack, and a reliable localhost server for HTML that pulls pinned CDN libraries. Use when turning a review/architecture/cost markdown doc into an interactive HTML view, when a diagram needs real cloud provider icons, when serving local HTML that file:// breaks, or when building a data-driven graph/chart view. Skip when the deliverable is plain mermaid-in-markdown authoring with no HTML companion, or a Python-rendered architecture diagram image.
Introspect Claude Code sessions - query conversation history, tool usage, event trees, and costs. Use when reviewing past sessions, debugging failures, or recovering user intent post-compaction.
Documentation quality skill with three modes: (1) AUDIT — fan out parallel subagents to corroborate that docs still reflect the reality of the code (commands run, paths exist, signatures match, claims hold) and produce a drift report; (2) WRITE/IMPROVE — author or rewrite docs using the researched lens taxonomy (Diátaxis + distilled style principles from great OSS docs), optionally in the maintainer's personal voice; (3) RESTRUCTURE — reorganize an existing doc, spec, or plan file for structural readability (heading hierarchy, list/table discipline, whitespace rhythm, BLUF) without changing its claims. Use when the user asks to check/audit docs, fix stale docs, write or improve documentation, restructure a doc/spec/plan for readability, or says 'gooddocs'. Add 'voice' to the invocation to write in the maintainer's voice; default is the neutral researched style.
Render and analyze Mermaid.JS diagrams embedded in markdown files. Enforces visual complexity limits AND WCAG color-contrast requirements via automated analysis. Every diagram MUST derive its palette from `resources/color_theming.md` and pass `scripts/mermaid_contrast.ts` before being declared done. Use when creating or updating architecture diagrams, analyzing diagram complexity, improving documentation clarity, or exploring a codebase to produce dual-density architecture diagrams for a README.
Playbook for building and extending project-local developer CLIs and the recurring assets they generate, so the same patterns are never re-derived from scratch. Use when: scaffolding or adding a subcommand to a repo CLI (argparse/Typer, project-root discovery, packaged assets); generating a STATIC HTML single-page viewer (client-side SPA routing, collapsible sidebar, light/dark + rebrandable design-tokens theming, Cytoscape graph or Plotly chart, generate/serve, --inline single-file, --archive zip); templating GitHub Actions workflows from a base template (create/update/validate, trigger-path glob distillation, reusable composite-action assets); using git worktrees to act on another branch/ref safely; autogenerating SVG/PNG diagrams from a stencil pack; or automating sticky PR comments and embedding a CI-run artifact image in a PR comment. Skip for non-CLI app code, or one-off scripts with no reuse. Invoke as /cli or when the user names one of these patterns.
Script-driven gap-analysis planning: a deterministic state machine (pgsm.py) owns the phases of a tiered gap-analysis spec — bootstrap → refinement → validation → decomposition → execution → complete — with evidence-based transition gates, per-state-only instructions composed into a single prompt, durable pause/resume state, and session-log forensics. Use for long-horizon work-breakdown planning where phase tracking must not live in the model's head. Requires uv. Skip for quick single-file plans (use plan-gap) or when no plan document is wanted.
| name | plans |
| description | Manage hierarchical planning documents with token-budgeted lazy loading, automatic rebalancing, and cascading context injection. Use when working with large planning docs, splitting oversized plans, or loading plan hierarchies into context efficiently. |
| allowed-tools | ["Read","Write","Bash(.claude/skills/plans/scripts/plan_manager.sh *)"] |
| user-invokable | true |
Manage markdown planning documents with YAML frontmatter, token-budgeted lazy loading, and automatic rebalancing.
# Add frontmatter metadata to a plan document
.claude/skills/plans/scripts/plan_manager.sh init docs/plans/my-plan.md
# Show section tree with token estimates
.claude/skills/plans/scripts/plan_manager.sh analyze docs/plans/my-plan.md
# Load cascading context from a plan hierarchy
.claude/skills/plans/scripts/plan_manager.sh context docs/plans/my-plan.md --depth 2
# Split oversized documents into children
.claude/skills/plans/scripts/plan_manager.sh rebalance docs/plans/my-plan.md --threshold 4000
# Update summary and token estimate metadata
.claude/skills/plans/scripts/plan_manager.sh update-summary docs/plans/my-plan.md --propagate
init <file> [--title TITLE]Add YAML frontmatter to an existing markdown file. Auto-detects the title from the first heading and generates a heuristic summary. Preserves existing frontmatter values.
analyze <file> [-f tree|json]Parse a plan document and display its section tree with per-section and total token estimates. Validates the document as CommonMark using marko. Default output is a visual tree; use -f json for structured output.
context <file> [-d DEPTH] [--max-tokens N] [--summaries-only]Emit cascading context for a planning doc hierarchy. Controls how much of the hierarchy to load:
The --max-tokens budget (default 8000) prevents overloading context.
Use --summaries-only to emit only frontmatter summaries (no document bodies) — useful for quick hierarchy inspection.
rebalance <file> [--threshold N] [--min-section N] [--dry-run]When a document exceeds the token threshold (default 4000), extract the largest sections into child markdown files. Each child gets its own frontmatter with summary, parent link, and token estimate. The parent section is replaced with a summary link.
Section extraction uses the marko AST to ensure splits never occur inside code fences. Both parent and child files are validated as valid CommonMark after the split.
Use --dry-run to preview without modifying files.
update-summary <file> [--propagate]Update the frontmatter summary and token_estimate fields using claude -p for AI-generated summaries. Requires the Claude Code CLI.
With --propagate, performs bidirectional tree traversal: recurses DOWN to all leaf children first, updates each summary from leaves up, then bubbles changes back to the root.
Every plan document uses this YAML frontmatter:
---
id: "uuid-v4"
title: "Document Title"
summary: "2-4 sentence summary for LLM context injection."
status: draft | active | complete | blocked
parent: "../parent.md"
children:
- "./child-a.md"
- "./child-b.md"
token_estimate: 4200
created: "ISO8601"
updated: "ISO8601"
tags: []
---
init it to add frontmatteranalyze to see which sections are largestrebalance to extract sections into childrencontext to get token-budgeted views of the hierarchyupdate-summary --propagate to keep metadata fresh