plan-interview

Walk each decision branch in an implementation plan with focused questions and codebase exploration

Generate developer-friendly documentation at docs/<slug>.md from a completed plan file, synthesized from the plan body, live code inspection, and git history

Convert a markdown file or plan to a rich, self-contained HTML document viewable in any browser

Scan plan directories for randomly-named files and rename them to descriptive kebab-case names based on content headings

Stress-test a plan through a structured conversational interview before implementation begins.

Batch documentation agent that scans the plans directory for completed plans without corresponding documentation in docs/, then invokes the documenting-plans skill for each one. Use when delegating bulk plan documentation, running a scheduled weekly documentation sweep, or generating docs for all completed plans at once. Not intended for documenting a single plan — use the documenting-plans skill directly for that.

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.