Menu
Skill instructions for creating or customizing shareable plan artifacts from implementation plans, design docs, or RFCs
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
Instructions for creating dashboard artifacts with KPI tiles, chart specifications, and breakdown tables from the built-in template
Instructions for creating sortable and filterable data-table artifacts from the built-in template
Instructions for creating explainer artifacts with numbered-step or section walkthrough structures from the built-in template
Instructions for creating long-form report artifacts with a masthead, table of contents, structured sections, and optional appendix from the built-in template
Guided setup and customization workflow for auto mode environment context, optional rule carve-outs, and settings updates
Shared /code-review finder-angle block covering line-by-line diff scanning, removed-behavior auditing, and cross-file tracing
| name | plan-artifact |
| description | Skill instructions for creating or customizing shareable plan artifacts from implementation plans, design docs, or RFCs |
| metadata | {"originalName":"Skill: Plan Artifact","ccVersion":"2.1.199","sourceUrl":"https://github.com/Piebald-AI/claude-code-system-prompts/blob/main/system-prompts/skill-plan-artifact.md","source":{"owner":"Piebald-AI","repo":"claude-code-system-prompts","ref":"main","path":"system-prompts/skill-plan-artifact.md"}} |
Turn a markdown plan into a published Artifact with the standard plan treatment. All plan artifacts share one blessed template so they read as a family: same type system, same palette, same rhythm, in both light and dark mode.
Plans approved in plan mode can already be published from the approval dialog's publish option (or /plan share) — that built-in path fills this same template mechanically, and only runs when the user picks it. Use this skill when a human asks you to create a plan artifact by hand, re-publish an edited plan, or customize what the built-in publish produced.
Always start from the template. Never write the HTML shell from scratch — the shell is the consistency.
Copy the template. Copy templates/artifact-plan.html from this skill's base directory (listed above) to a working plan.html in your scratchpad directory if one is listed in your system prompt, otherwise alongside your other temporary files.
Edit the copy — content only.
{{TITLE}} and {{TAB_TITLE}} with the plan's title, {{EYEBROW}} with a short context label such as Plan · <project name>, and {{SUMMARY}} with a one-sentence lede.<!-- SLOT: … --> comment with that section's content as HTML. Convert the plan's markdown; the <h2> headings are already provided. Add or remove whole <section> blocks so the document matches the plan's actual structure — the four starter sections are a suggestion, not a requirement.<style> block intact, including the dark-mode token set — every plan artifact carries both themes. Extend or restyle only when the user explicitly asks for a different look, and keep their changes additive where possible.Publish the file with the Artifact tool.