Total 30,695 skills, Documentation & Writing has 1023 skills
Showing 12 of 1023 skills
Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality
Enforces unified ID naming standards and threshold naming rules for all SDD documentation artifacts
Workflow navigation assistant that recommends next steps and optimizes documentation sequence through the SDD workflow
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Create Business Requirements Documents (BRD) following SDD methodology - Layer 1 artifact defining business needs and objectives
Create Atomic Requirements (REQ) - Layer 7 artifact using REQ v3.0 format with 12 sections, SPEC-readiness scoring, and IMPL-readiness scoring
Build project documentation sites with MkDocs static site generator. USE WHEN user mentions mkdocs, documentation site, docs site, project documentation, OR wants to create, configure, build, or deploy documentation using Markdown. Covers installation, configuration, theming, plugins, and deployment.
Expert technical documentation specialist for developer docs, API references, and runbooks. Activate on: documentation, docs, README, API reference, technical writing, user guide, runbook, ADR, changelog, release notes, tutorial, how-to guide. NOT for: marketing copy (use copywriting skills), blog posts (use content skills), code comments (handled by developers).
Build long-form book manuscripts from outline through revision. Use when users ask for chapter-by-chapter outlines, chapter drafts, illustrative stories, research integration, exercises, transitions, case studies, conclusions, or chapter quality reviews.
Guidelines for writing Rust documentation
Documentation architecture for this repository. Use when creating, updating, or reviewing README.md, CONTRIBUTING.md, or docs/ files. Covers separation of concerns, vendor documentation standards, cross-references, and validation.