Generate documentation for a completed atomic task — inline component doc and/or ADR depending on scope area. Thin wrapper around doc-generate invoked automatically by plan-task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-planning-with-ai:doc-task <NNN-slug> <scope-NN> <task-NN><NNN-slug> <scope-NN> <task-NN>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate documentation for a completed atomic task. This is a thin wrapper around `/doc-generate` invoked automatically by `/plan-task` after each task completes. Can also be invoked manually to regenerate docs for an already-completed task.
Generate documentation for a completed atomic task. This is a thin wrapper around /doc-generate invoked automatically by /plan-task after each task completes. Can also be invoked manually to regenerate docs for an already-completed task.
The area code (WB, AP, IN, AG, DO, W, or custom) determines which documents are generated: inline component docs, ADRs, changelogs, or user guides. Tasks in area DO (documentation) or W (workflow) exit silently and produce no output.
$ARGUMENTS — format: NNN-slug scope-NN task-NN
NNN-slug — planning id (e.g. 001-user-auth-api)scope-NN — scope id (e.g. scope-01)task-NN — task id (e.g. task-3)$ARGUMENTS into planning-id, scope-id, and task-id..planning/active/<planning-id>/02-deepening/<scope-id>-*.md to determine the area code.
Area: or Repository Area: field (case-insensitive).DO or W: exit silently — no output, no files written./doc-generate <planning-id> <scope-id> <task-id>.doc-generate verbatim as this skill's report.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub cmartinezs/claude-planning-with-ai --plugin claude-planning-with-ai