Menu
Create a pragmatic self-contained HTML plan that organizes the user's plan content visually without expanding the scope unnecessarily.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run the canonical build plus all nine per-project test commands from docs/TESTING.md. Never uses solution-level dotnet test.
Create or re-baseline lean, repository-grounded implementation plans and persistent dev docs when users ask for an implementation plan, technical plan, feature plan, refactor plan, or dev-docs workstream.
Senior CTO review workflow for repository-grounded implementation-plan workstreams used before coding.
Apply project EF Core conventions for repositories, DbContext setup, query filters, migrations, and seeded lookup data.
Create a self-contained HTML artifact focused on a high-quality SVG architecture or system diagram with minimal supporting prose.
Create a self-contained HTML artifact for reports, explainers, comparisons, prototypes, or decks when no narrower HTML diagram or plan skill applies.
| name | html-plan |
| description | Create a pragmatic self-contained HTML plan that organizes the user's plan content visually without expanding the scope unnecessarily. |
| type | workflow |
| enforcement | suggest |
| priority | low |
| disable-model-invocation | true |
Create one self-contained HTML file that turns a plan into a clear, practical, visually organized artifact. Keep the writing close to the user's intent while improving grammar, structure, and scanability.
html-diagram is the better fit.html is the better fit.dev/active/; use the project planning workflow instead.references/html-effectiveness/:root and html.dark.localStorage and apply before paint from the document head.Use for: "Turn this launch plan into a clean HTML page."
Avoid for: "Create repository dev docs for this feature."