Stats
Actions
Tags
From inki
Generates a documentation page outline from a topic brief and a template, then saves it as a Markdown file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:outline <topic brief or path to a brief file><topic brief or path to a brief file>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS` is either inline text or a path to a `.md` file containing the brief.
$ARGUMENTS is either inline text or a path to a .md file containing the brief.
Decide which template applies (feature, plugin, guide, API, configuration, breaking-change) based on the brief. Read the relevant template at ../../references/templates/<template>-template.md.
Read ../../references/prompts/outliner.md and ../../references/prompts/outline-generator.md. Use them as system prompts to produce an outline.
Display the outline. Wait for y (accept) / n (discard) / e (edit inline).
On y, save the outline as a .md file at a path the user confirms (typically under docusaurus/docs/<area>/<slug>.outline.md).
npx claudepluginhub strapi/documentation --plugin inkiGenerates a documentation page from an approved outline, matching template, and authoring guide. Useful for technical writers following a structured documentation workflow.
Creates new documentation pages using standard templates and STYLE.md conventions. Supports skill, hook, config, guide, concept, and index types with smart type detection.
Creates detailed section outlines in a progressive writing workflow, enforcing outline-before-prose. Evaluates section structure against PRECIS claims and gates prose drafting until review is passed.