From kdoc
Create a page, screen, or flow specification by detecting the active pack, reading the relevant template, and writing a schema-aware design doc. Use when the user asks to create a page spec, create a screen spec, create a design spec, or create a flow spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kdoc:design-create-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to create design specifications without relying on CLI commands.
Use this skill to create design specifications without relying on CLI commands.
.kdoc.yaml to detect installed packs and available scopes.core/schema/frontmatter-schemas.json for the closest matching frontmatter contract used by the target design document.packs/nextjs/templates/page-spec.md or packs/nextjs/templates/flow-spec.mdpacks/swift-ios/templates/screen-spec.md or packs/swift-ios/templates/flow-spec.mdcore/templates/flow-spec.mdkdoc_validate. The skill must still work without MCP.kdoc:tldr-createkdoc:governance-checknpx claudepluginhub mariogusmao/mg-plugins --plugin kdocScaffolds feature specs from project template by guiding through sections like Problem, Approach, Happy Path, Edge Cases. Use for planning non-trivial features or missing design docs.
Writes OpenSpec design.md and tasks.md artifacts for spec-driven features. Useful when producing technical designs or task checklists from a proposal.