Extract every PlantUML block from docs/specs/<slug>.md and render each to SVG under docs/specs/_rendered/<slug>/, with an index.md listing them in order. Run this before /approve-direction so the reviewer sees pictures instead of raw PlantUML.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
User-invokable only. This skill has side effects (writes SVGs and an index). Claude does not invoke it autonomously.
/spec-render <slug> — where <slug> corresponds to docs/specs/<slug>.md.
java on PATH (JDK 8+) + the pinned plantuml.jar at .claude/bin/plantuml.jar (fetched at install time; SHA-verified). The render script invokes java -jar .claude/bin/plantuml.jar -tsvg ... and exits 2 with a named remedy if either dep is missing.docs/specs/<slug>.md exists and passes spec_diagram_presence_guard + plantuml_syntax_guard — otherwise rendering will surface the same errors.docs/specs/<slug>.md must exist.node .claude/skills/spec-render/render.mjs <slug>
docs/specs/<slug>.md.plantuml fenced block in source order.docs/specs/_rendered/<slug>/<NN>_<kind>.puml, then renders to <NN>_<kind>.svg.docs/specs/_rendered/<slug>/index.md with section titles and image links in order.docs/specs/_rendered/<slug>/<NN>_<kind>.svg — one per diagram block.docs/specs/_rendered/<slug>/<NN>_<kind>.puml — source kept next to the SVG for easier diffs.docs/specs/_rendered/<slug>/index.md — markdown index with embedded images.docs/specs/_rendered/ to .gitignore if you don't want the SVGs in the repo; the PlantUML sources in the spec are the source of truth.plantuml MCP server from .mcp.json — it talks to a PlantUML renderer over HTTP. This skill prefers the local java -jar path because it's faster, keeps renders self-contained, and uses the SHA-pinned jar (so the version a consumer renders against matches what this baseline was tested with).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
The English summary is being prepared. Showing the original description.
Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.
The English summary is being prepared. Showing the original description.
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
The English summary is being prepared. Showing the original description.
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.
The English summary is being prepared. Showing the original description.
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
The English summary is being prepared. Showing the original description.
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
The English summary is being prepared. Showing the original description.