Execute increment implementation following spec and plan - hooks run after EVERY task

Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format

doc-auditor

Guide a user through authoring a new document using the GoodDocs template and validation rules.

Documentation automation with file versioning and metadata. Use for maintaining documentation, tracking file versions, adding metadata headers.

Layer 4 artifact for Behavior-Driven Development test scenarios using Gherkin Given-When-Then format

Create Business Requirements Documents (BRD) following SDD methodology - Layer 1 artifact defining business needs and objectives

Checks if code changes require documentation updates

This skill provides guidance for maintaining documentation consistency with implementation in the vscode-sidebar-terminal project. Use this skill when creating or updating documentation, verifying documentation accuracy, preparing releases, or when the codebase has changed and documentation may need updates. This skill should be used proactively after implementing features or bug fixes.

Create Data Contracts (CTR) - Optional Layer 9 artifact using dual-file format (.md + .yaml) for API/data contracts

Loads feature docs, workflow docs, and invariants before planning any task. Use when starting complex work, changing multiple features, or when unsure about constraints. Essential first step for non-trivial changes.

Diagnose documentation issues (format, links, content)

Create EARS (Easy Approach to Requirements Syntax) formal requirements - Layer 3 artifact using WHEN-THE-SHALL-WITHIN format

Deep expertise for documentation lifecycle orchestration. Quality assessment frameworks, workflow patterns, delegation protocols, and release checklists. Auto-loads for doc-expert agent.

Fetch library and framework documentation via context7-mcp and fetch-mcp

Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.

Reference for The Fold's typed comments and doc forms system. Use when adding type annotations, documentation, todos, or other metadata to Scheme code. Covers (doc ...) syntax, standard tags, search commands, and type checker integration.

Generate Architecture Decision Records (ADRs) to document significant architectural decisions. Use when making important technical decisions that need documentation.

Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.

Locate and retrieve specific documentation sections from DiPeO's docs/ by heading anchors or keywords. Returns minimal, targeted excerpts instead of full files. Use when you need precise documentation context without loading entire guides.

Maintain documentation (sync, cleanup, update)

Maintains high-quality, concise, project-aligned documentation. Creates, updates, and validates README.md, CLAUDE.md, code comments, and other documentation. Activates after implementing features, when documentation is outdated, or when explicitly requested.

doc-maintenance

Documentation lifecycle management skill. Activates when user mentions documentation, docs, sync, quality, validation, releases, or setup. Routes to appropriate agent (doc-expert for orchestration, doc-writer for content) and provides gentle reminders about documentation health.

Enforces unified ID naming standards and threshold naming rules for all SDD documentation artifacts

Apply Progressive Disclosure principles to organize large documentation projects. Restructure docs into hierarchical structure, reduce token usage by 95%+, and create README files for navigation.

Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs

>-

Targeted query capabilities for machine-readable codebase documentation with cross-reference tracking, call graph analysis, and workflow automation. Enables fast lookups of classes, functions, dependencies, and function relationships without parsing source code.

Create Reference Documents (REF) - supplementary documentation that doesn't participate in formal traceability chain

Create Atomic Requirements (REQ) - Layer 7 artifact using REQ v3.0 format with 12 sections, SPEC-readiness scoring, and IMPL-readiness scoring

Reviews documentation for completeness, accuracy, and consistency with the project's DX_GUIDE.md standards. Validates documentation structure, checks for broken links, ensures examples are up-to-date, and verifies technical accuracy. Use when creating or updating documentation, reviewing doc-heavy PRs, or ensuring doc quality.

Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance. Auto-activates when user asks to review, understand, or explore a codebase, when starting work in a new project, when asking about conventions or agents, or when documentation context would help. Can consolidate multiple platform docs into unified AGENTS.md.

Token-efficient documentation search using Serena Document Index. 90%+ token savings vs reading full files. Use BEFORE reading README.md or docs/ files. Triggers on architecture questions, pattern lookups, and project-specific documentation needs.

Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications

A SKILL.md file that defines a Claude Code skill with metadata, instructions, and examples

Maintains the CLAUDE.md navigation hierarchy and optional README.md architecture docs across a repository. This skill is self-contained and performs all documentation work directly.

Create System Requirements (SYS) - Layer 6 artifact defining functional requirements and quality attributes

Create Task Breakdown (TASKS) - Layer 11 artifact decomposing SPEC into AI-structured TODO tasks

Update development blog with implementation milestones, learnings, and progress. Use after completing major milestones or phases.

Updates documentation after code changes to keep docs in sync with code reality. Use AFTER implementation is complete. Covers feature docs, workflow docs, and index files.

Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.

>

- [ ] Installation instructions present

DocETL is a system for creating LLM-powered data processing pipelines. This skill helps you build end-to-end pipelines: from data preparation to execution and optimization.

SOTA Docker/Compose architecture, implementation, refactor, and security hardening. Use when working on containerization tasks such as creating or rewriting Dockerfiles, docker-compose files, buildx/bake configs, .dockerignore, and CI pipelines for build/test/scan/publish; auditing existing container setups for security, correctness, size/perf, and best practices (least privilege, non-root, minimal images, pinned base images, BuildKit secrets, healthchecks); debugging Docker build/run issues; or designing dev vs prod compose workflows across services (DB/cache/queues) with correct networking, volumes, secrets, and resource limits.

Docker containerization patterns for Node.js applications. Use when containerizing backend services.

Dockerizes backend projects with auto-detection, latest base images via web search, Dockerfile generation, and Makefile with port override support.

Apply when containerizing applications: writing Dockerfiles, docker-compose configurations, and multi-stage builds.

Create optimized Dockerfiles with multi-stage builds, security hardening, layer caching, and health checks. Includes docker-compose patterns for development and production environments.