Stats
Actions
Tags
From sdlc-workflow
Use when a documentation request is ambiguous, involves planning a docs structure, or a page seems to mix multiple purposes. Classifies content into Diátaxis quadrants (tutorial, how-to, reference, explanation), proposes a documentation map, and produces a writing plan with ordering. Triggers on phrases like "plan my docs", "what docs do I need", "help me organise my documentation", "docs architecture", "I need to write docs for my project", or when a user asks for a README and a full docs set together.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sdlc-workflow:diataxis-doc-plannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when a request is about "docs", "documentation", "README", "guides", "reference", or "improving the docs" but the correct form is unclear.
Use this skill when a request is about "docs", "documentation", "README", "guides", "reference", or "improving the docs" but the correct form is unclear.
This skill classifies the work using the Diátaxis model, proposes the right document types, and creates a practical writing plan.
Diátaxis separates documentation into four kinds:
The first classification question is not "what topic is this?" but "what does the reader need right now?"
Use this decision table:
Use this skill when:
Do not use this skill when the target format is already obvious and the user wants the content written immediately. In that case route directly to the specific writing skill.
Collect or infer:
Treat README as a landing page, not a quadrant.
A README may include:
A README must not try to fully replace all four quadrants.
Return:
Classification table
Proposed docs structure
Writing order
Risks and likely boundary violations
Flag and fix these:
A good plan should make it obvious:
If that is not obvious, the docs map is still wrong.
npx claudepluginhub jayteealao/agent-skills --plugin sdlc-workflowOrganizes project documentation using the Diátaxis framework (tutorials, how-to guides, reference, explanation). Use when auditing, structuring, or restructuring a knowledge base.
Authors technical documentation through a repeatable workflow: audience analysis, Diátaxis-mode selection, structure, draft, review, publish. Covers READMEs, ADRs, API docs, and runbooks.
Provides Diataxis four-quadrant docs framework: tutorial/how-to/reference/explanation definitions, classification decision tree, matrix, and signals for content categorization.