Guides

Visual Docs / 4 min read

Turn a migration plan into something you can explore.

Make dependencies, assumptions, and decisions visible without losing the source.

Start with an existing plan

Visual Docs transforms supplied analysis into an interactive document. Give it the migration plan, review, or architecture notes you already have. Include known dependencies, release criteria, constraints, and unresolved questions. The plugin presents the material; it does not independently prove that the plan is correct.

Name the decisions the document should support

A useful visual document helps someone answer a practical question. Which task blocks launch? What can run in parallel? What changes if team capacity drops? Tell the skill which relationships matter and ask it to preserve the evidence for each claim.

Separate facts from scenario assumptions

A scenario control should expose its formula and limits. In our demonstration, delivery time is the ceiling of 24 person-days divided by team size. That deliberately simple estimate excludes coordination, sequencing, and uncertainty. It is an illustration, not a delivery forecast. Real plans need a model that reflects their constraints.

Explore and check the dependencies

Select a node and follow its incoming relationships. Review should wait for the API work and the data migration; launch should wait for review. Cross-check every edge against the source plan. Missing or invented dependencies can make an attractive diagram misleading.

Keep the document portable

Request the offline HTML artifact and its Markdown companion. The HTML is useful for people exploring the plan; the Markdown preserves an agent-readable handoff. Keep the two together when sharing or updating the work so decisions do not lose their context.

Know the host boundary

The repository records the Visual Docs portable creation core as verified in Codex when its whole skill folder is retained. Its optional marketplace update hook remains unverified there. Use the documented host-specific setup and validate the actual output in your environment.

Installation

Run these commands inside Claude Code. Copying a command does not install anything. 1. Add the marketplace

Claude Code
/plugin install visual-docs@alsheddi-claude-marketplace

Search titles, capabilities, and guides. Use Tab to choose a result, Enter to open it, and Escape to close.

Installation

Make it part of your toolkit.

Run these commands inside Claude Code. Copying a command does not install anything.

1. Add the marketplace

Claude Code
/plugin marketplace add nawafSheddi/alsheddi-claude-marketplace
Claude Code
/plugin install chartwise@alsheddi-claude-marketplace

Claude Code · Codex

Read the full installation guide