documentation-criteria
Documentation Criteria provides decision matrices and templates to identify which technical documents your feature or change requires. Use it to navigate PRD, ADR, UI Spec, Design Doc, and Work Plan creation based on scope, complexity, and architectural impact.
Documentation Criteria helps you determine which technical documents—PRD, ADR, Design Doc, Work Plan—are required for your feature or change.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-28
Documentation Criteria helps you determine which technical documents—PRD, ADR, Design Doc, Work Plan—are required for your feature or change. Documentation Criteria provides decision matrices and templates to identify which technical documents your feature or change requires. Use it to navigate PRD, ADR, UI Spec, Design Doc, and Work Plan creation based on scope, complexity, and architectural impact.
Use it when
- Documentation Criteria offers templates for five key technical documents: Product Requirements Document (PRD).
- Documentation Criteria provides a decision matrix to help you determine exactly which documents your project requires based on scope.
Verify before relying
Read SKILL.md below before installing (7 files). Open directory: indexed for reading, not audited.
Install
shinpr/claude-code-workflows/documentation-criteria · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
When do I need an ADR architecture decision record?
Documentation Criteria helps you determine when an Architecture Decision Record is mandatory for your project. An ADR is typically required when your feature or change involves significant architectural decisions, system design choices, or technical trade-offs that affect multiple components or future development. Use Documentation Criteria's decision matrices to assess your feature's scope and complexity, then follow the provided ADR template to document the decision, context, and rationale.
What technical documentation templates does Documentation Criteria provide?
Documentation Criteria offers templates for five key technical documents: Product Requirements Document (PRD), Architecture Decision Record (ADR), Design Doc, UI Specification, and Work Plan. Each template is tailored to guide you through the essential sections and content structure needed for that document type. Access all templates directly within Documentation Criteria to ensure consistency across your technical projects.
How many documents do I need for my project?
Documentation Criteria provides a decision matrix to help you determine exactly which documents your project requires based on scope, complexity, and architectural impact. Not every project needs all five document types—Documentation Criteria guides you through the assessment process so you create only the necessary documentation without over-documenting or missing critical specs.
What's the correct creation order and dependencies for technical docs?
Documentation Criteria clarifies the creation order and dependencies between technical documents. Typically, the PRD establishes requirements first, followed by architectural decisions (ADR if needed), then design specifications and UI specs, with the Work Plan coordinating execution. Documentation Criteria's templates and guidelines show how each document builds on previous ones to ensure logical flow and consistency.
How do I determine which technical documents are required for a feature?
Documentation Criteria provides decision matrices and acceptance criteria to help you determine which technical documents your feature requires. Assess your feature's scope, complexity, and architectural impact using Documentation Criteria's framework, then follow the recommended document set. The tool also includes verification strategy requirements to ensure your documentation meets quality standards.
What should a design doc template for software features include?
Documentation Criteria's design doc template guides you through essential sections including problem statement, proposed solution, architectural overview, implementation details, dependencies, and trade-offs. The template helps you structure technical specifications clearly so stakeholders and developers understand the feature's design rationale and can execute implementation confidently.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Documentation Creation Criteria
Templates
- prd-template.md - Product Requirements Document template
- adr-template.md - Architecture Decision Record template
- ui-spec-template.md - UI Specification template (frontend/fullstack features)
- design-template.md - Technical Design Document template
- plan-template.md - Work Plan template
- task-template.md - Task file template for implementation tasks
Creation Decision Matrix
| Condition | Required Documents | Creation Order |
|---|---|---|
| New Feature Addition (backend) | PRD → [ADR] → Design Doc → Work Plan | After PRD approval |
| New Feature Addition (frontend/fullstack) | PRD → UI Spec → [ADR] → Design Doc → Work |
(truncated - see the full file via the links below)
File tree — 7 files
skills/documentation-criteria/SKILL.md
skills/documentation-criteria/references/adr-template.md
skills/documentation-criteria/references/design-template.md
skills/documentation-criteria/references/plan-template.md
skills/documentation-criteria/references/prd-template.md
skills/documentation-criteria/references/task-template.md
skills/documentation-criteria/references/ui-spec-template.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Determine which technical documents are required for a feature or change”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Create Adr Spike walks you through a five-phase process—Research, Analysis, Decision, Documentation, and Memory Storage—to evaluate technical alternatives and formalize architectural choices. It manages ADR lifecycle with proper numbering, integrates external research tools, and persists decisions to a memory graph for future reference.
prd converts feature requests into structured Product Requirements Documents, delivering actionable outcomes and concrete decisions. It's designed for executable documentation tasks, not high-level strategy or planning discussions.
Architecture Designer guides you through system design from requirements to documented decisions. It creates architecture diagrams, evaluates technology trade-offs, and produces Architecture Decision Records for key choices. Use it to structure microservices, plan scalability, and validate designs with stakeholders.
doc-prd generates a Product Requirements Document as Layer 2 of the SDD workflow, converting business requirements into product capabilities, user personas, and measurable success criteria. It structures features and acceptance criteria at the container level, sitting between upstream BRD and downstream EARS artifacts.
adr-author guides you through structured architecture decision authoring in three phases: Frame captures scope and drivers, Decide evaluates options and rationale, and Govern writes the final ADR file with lineage tracking. Choose between compact Y-Statement or detailed MADR v4.0.0 output, and enter via interactive capture, planner handoff, or template adoption.
This skill provides templates and guidance for creating Architecture Decision Records—lightweight documents that preserve the reasoning behind major technical choices. It walks you through the Nygard format, covering context, decision, consequences, and alternatives, plus best practices for lifecycle management and team review. Use it when evaluating trade-offs or recording decisions that shape your system's future.
More skills deliver-prd (Apache-2.0)