Menu
Draft a documentation page from an approved outline, the matching template, and the relevant authoring guide.
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
| name | draft |
| description | Draft a documentation page from an approved outline, the matching template, and the relevant authoring guide. |
| argument-hint | [--no-log] <path to outline file> |
| user-invocable | true |
$ARGUMENTS is a path to an outline file produced by /inki:outline.
Logging: unless --no-log is passed, write this skill's report to the run log per ../../references/logging.md (--log-dir <path> and --short-log are also accepted). When invoked as part of an orchestrator (e.g. /inki:write), write into that run's existing directory instead of creating a new one.
../../references/templates/<template>-template.md../../references/authoring/AGENTS.<area>.md../../references/12-rules-of-technical-writing.mdRead ../../references/prompts/drafter.md. Use it as the system prompt. Generate the draft, section by section.
Save the draft as a .md file at the canonical path (drop the .outline.md suffix, use .md). Show the user the file path and a diff.
Top-level review orchestrator: runs style-check, outline-check, outline-ux-analyzer, code-verify, coherence-check, and pitfalls-check on a file, directory, or PR.
Create a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.
End-to-end documentation orchestrator: chains all four inki phases (research, write, review, submit) for a single subject. Gates between each phase by default; --non-interactive chains without pauses and runs a review-fix loop. The simplest way to document a subject from scratch.
Generate an outline for a new documentation page from a topic brief and the appropriate template.
Add a new entry to the known-pitfalls catalog that pitfalls-check audits against. Verifies the correct pattern against the Strapi source before adding, and confirms with the user. Use when you have found a documentation mistake worth catching automatically in future reviews.
Rewrite the title or description/body of one or more open PRs on strapi/documentation to match git-rules.md. Strict one-by-one confirmation, or auto-edit with --non-interactive.