documentation-standards

Generate standardized templates and structures for project documentation and ADRs.

59|12|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill documentation-standards-etylsarin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-standards
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/skills/documentation-standards
Command: npx skills add https://github.com/etylsarin/opencastle --skill documentation-standards-etylsarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation templates, structure, and writing standards to ensure consistency across project docs, roadmaps, ADRs, and known issues.

Core Features & Use Cases

  • Templates for common doc types (README, ADRs, roadmaps)
  • Structure guidance and writing standards to improve clarity and consistency
  • Use Case: teams can quickly generate conformant docs with minimal friction

Quick Start

Follow the documentation standards to create consistent project docs and ADRs in your repository.

Frequently Asked Questions about documentation-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create standardized ADR and README templates for my software project?

You can create standardized ADR and README templates by applying predefined documentation structures that enforce front matter usage and writing standards. This ensures consistency across project docs and architecture decision records with minimal friction.

What writing standards should I use for project documentation and roadmaps?

Effective writing standards for project documentation include structure guidance for roadmaps, ADRs, and READMEs, along with specific changelog and diagram guidelines. Applying these standards improves clarity and consistency across all knowledge repositories.

Can I use these documentation templates for issue tracking and knowledge repositories?

Yes, you can use these documentation templates for issue tracking and knowledge repositories. The standards provide specific structures for issue templates and knowledge bases, ensuring all project documentation remains conformant and consistently formatted.

What is the best way to structure architecture decision records and project roadmaps?

The best way to structure architecture decision records and project roadmaps is to use standardized templates with required front matter. This approach enforces consistent writing standards and structure guidelines across all software project documentation.

Do I need front matter in my README and ADR templates to maintain documentation standards?

Yes, front matter is required in README and ADR templates to satisfy documentation standards. Using front matter ensures your project docs adhere to the standardized structures needed for consistent roadmaps and knowledge repositories.