agentics-kit

Turns a vague idea into a decision-complete proposal — researches web + codebase, separates facts from decisions — use when the user floats an idea, asks should-we, or wants to compare and align.

Marks a plan as completed. Inspects codebase evidence, confirms with the user, ticks acceptance criteria in the Markdown spec, and re-renders the HTML; --all sweeps done-but-unmarked plans. Use via /plan-agent:finalize-plan.

Generates HTML implementation-plan documents. Produces a self-contained .html plan file with steps, acceptance criteria, and metadata. Use when the user asks to create or generate an HTML plan file.

Generates a runnable static-HTML prototype from a plan, idea, image, or Figma design. Produces one self-contained, framework-free clickable file under docs/prototypes/. Use when asked to prototype a plan, idea, screenshot, mockup, or design file.

Builds structured AI prompts using Anthropic techniques. Interviews users, classifies prompt type, and delivers a copy-pasteable prompt. Use when the user asks to refine or build a prompt.

Plan review Agent Team. Reviews HTML implementation plans in parallel, synthesizes findings, and applies improvements in place. Use when the user asks to review or improve an implementation plan.

Installs the team's shared rule files into ~/.claude/rules/ with per-file confirmation. Copies plan-mode, component-driven-ui, typescript-jsdoc, and review-bot-loops rules plus the plan skeleton. Use when the user asks to sync, install, or update team rules.

Saves an HTML Artifact page to the local artifacts inbox for sharing. Copies a chosen .html into .claude/artifacts with a dated name, then publishes it to the deployed artifacts gallery. Use when asked to save or share an artifact.

Exports a Claude Code session transcript to Markdown in the plans directory. Converts session JSONL into readable reference material. Use when the user asks to export, save, or archive a session as Markdown.

Writes developer guides on any project topic. Covers rules, tools, resources, plans, and changes for any reader. Use when the user asks to write, explain, or deep-dive a project topic as a guide.

Stress-tests plan decisions node-by-node with focused questions. Walks each decision point surfacing assumptions and weak spots. Use when the user asks to deep grill or stress-test a plan.

Generates a prose reference doc from a completed plan. Inspects the codebase and git history to produce accurate, evidence-backed documentation. Use when the user asks to document a completed plan.

Converts a markdown file into a self-contained HTML page. Produces styled output with syntax highlighting and responsive layout. Use when the user asks to convert a markdown file or plan to HTML.

Stress-tests implementation plans through structured interviews. Surfaces gaps, risks, and assumptions via targeted questions. Use when the user asks to stress-test or validate a technical plan.

Writes lifecycle status into a plan file's frontmatter. Inspects the codebase and git history to set accurate dates and completion state. Use when the user asks to check or update a plan's status.

Runs a six-role Agent Team to review product plans in place. Covers PM, Dev, UX, Frontend, A11y, and Security on PRDs and proposals. Use when the user asks to review or improve a product plan.

Runs the full ship pipeline with CI polling and bounded autofix. Chains commit, PR, CI poll, and autofix in one supervised flow. Use when the user asks to autonomously ship or watch CI.

Deprecated alias for markdown-to-html. Delegates immediately to markdown-to-html with no additional processing. Use when the user asks to convert a plan to HTML.

Generates platform-aware social copy and a dark-mode card image for code changes. Detects from git, picks a template, and screenshots via Playwright. Use when asked to post or share a code change.