skills.rest
jamestorrevillas
jamestorrevillasCOMMUNITY
Explore all skills by this author →
GitHub

doc-creation

Generate technical documentation from structured prompts using frontmatter-driven templates.

3|4|Updated Mar 20, 2026
Search Tags:#documentation#adr#runbooks#api-reference#architecture-docs#readmes#style-guidelines
One-click install
npx skills add https://github.com/jamestorrevillas/dev-skills --skill doc-creation-jamestorrevillas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-creation
Source: https://github.com/jamestorrevillas/dev-skills/tree/main/.github/skills/doc-creation
Command: npx skills add https://github.com/jamestorrevillas/dev-skills --skill doc-creation-jamestorrevillas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps technical teams create consistent, high-quality documentation across READMEs, architecture docs, runbooks, ADRs, and API references, reducing onboarding time and maintenance burden.

Core Features & Use Cases

  • Generate READMEs, architecture docs, runbooks, ADRs, API references, and changelogs from structured prompts.
  • Enforce branding, templates, and writing style guidelines to ensure consistency across documents.
  • Use case: A team needs a complete architecture doc for a new microservice within a tight deadline.

Quick Start

Create a complete architecture doc for a new service using the provided templates and style guidelines.

Frequently Asked Questions about doc-creation

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

FAQPage Schema
How do I generate an architecture doc for a new microservice quickly?▼

Architecture docs enforce consistency by using frontmatter-driven templates and style guidelines, ensuring high-quality technical documentation that reduces onboarding time and maintenance burden.

What is the best way to create consistent API references and runbooks?▼

The best way to create consistent API references and runbooks is automating generation from structured prompts, enforcing branding and templates to maintain high-quality technical documentation.

Can I use frontmatter-driven templates to enforce style guidelines across READMEs and ADRs?▼

Yes, you can enforce style guidelines across READMEs and ADRs by applying frontmatter-driven templates, ensuring writing consistency and generating machine-readable sections for RAG systems.

When do I need machine-readable sections for RAG systems in technical documentation?▼

You need machine-readable sections for RAG systems when automating technical documentation creation, ensuring generated READMEs, runbooks, and API references are consistently structured for retrieval.

What are the limitations of generating changelogs from structured prompts?▼

Limitations of generating changelogs from structured prompts include strict adherence to enforced branding and templates, which may constrain flexibility but ensures consistency across software projects.

Related Skills

Explore More Content & Communication Skills→
BrunoSantanaDeveloperBrunoSantanaDeveloper

documentation-templates

Standardize project documentation with templates and structure guidelines.

Community
Basic
rikdcrikdc
2

document

Generate technical documentation from OpenAPI specs and code annotations.

Community
Intermediate
sunholo-datasunholo-data
33

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official
Intermediate
dt418dt418

Docs Pack

Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.

Community
Intermediate