visual-plan-review

Compare implementation plans against codebases to identify gaps and risks.

Updated Aug 12, 2018
One-click install
npx skills add https://github.com/ivanov-i/dots --skill visual-plan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-plan-review
Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/visual-plan-review
Command: npx skills add https://github.com/ivanov-i/dots --skill visual-plan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compare a proposed implementation plan against the current codebase to identify gaps and risks.

Core Features & Use Cases

  • Visual-diff style validation to ensure plan alignment with code
  • Pre-implementation risk analysis for RFCs, specs, and plans
  • Use Case: Validate a plan against a codebase to surface architectural conflicts and dependencies

Quick Start

Provide the plan path and optional codebase path to generate a visual HTML plan review page.

Frequently Asked Questions about visual-plan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an implementation plan against my codebase before coding?

Plan validation against a codebase involves comparing the proposed implementation text with current code to identify gaps and risks. This Skill reads your plan, builds a fact sheet from the text and code, and generates a visual HTML diff for review.

Can I do a visual risk analysis for an RFC or specification?

Yes, visual risk analysis for RFCs and specifications is the core use case. It compares the proposed spec against the existing codebase to surface architectural conflicts and dependencies, outputting a visual HTML page for review.

What is the best way to perform a gap analysis between a plan and existing code?

Gap analysis between a plan and code is best performed by building a fact sheet from both sources. This Skill uses the visual-explainer workflow to cross-reference the plan text with the codebase and outputs the visual diff to your browser.

How do I generate a visual HTML diff of my implementation plan?

Generating a visual HTML diff of your implementation plan requires providing the plan path and optional codebase path. The tool writes the output diagram to ~/.agent/diagrams/ and automatically opens it in your browser.

Does plan review require any external dependencies or components?

Plan review using this Skill requires no external dependencies or components. You only need to provide the path to your plan text and optionally specify the codebase path for the comparison to run.

When should I not use a visual plan review workflow?

Visual plan review is not suited for situations lacking a written plan or existing codebase to compare against. It requires textual plan documents and code to build a fact sheet and generate the visual diff output.