Docs Templates

Name: Docs Templates
Availability: InStock
Author: Pageel

Generate architecture, CLI, deployment, changelog, and strategy docs with source-verification checks.

48|18|Updated Feb 4, 2026

Search Tags:#architecture #templates #documentation #source verification #agent workflows #stale docs #graph documentation

Ready to run

npx skills add https://github.com/pageel/para-workspace --skill docs-templates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Docs Templates
Source: https://github.com/pageel/para-workspace/tree/main/templates/common/agents/skills/docs
Command: npx skills add https://github.com/pageel/para-workspace --skill docs-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents documentation drift and hallucinations by providing just-in-time templates and strict source-verification expectations for the /docs workflow.

Core Features & Use Cases

Sidecar doc templates for on-demand generation: Loads the right reference templates only when the agent is generating documentation.
Source-verification guardrails: Enforces a standardized verification header and a checklist to cross-check referenced source paths, exports, and env/config usage.
Graph-aware documentation support: Enables optional graph-enhanced docs behavior when .beads/graph/ exists, including traceability and stale-doc detection requirements.

Quick Start

Use the agent to run /docs new to generate architecture, CLI, deployment, changelog, and strategy documentation using the provided templates with required source-verification checks.

Frequently Asked Questions about Docs Templates

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

FAQPage Schema

How do I prevent stale documentation when generating agent workflows?▼

To prevent stale documentation in agent workflows, apply just-in-time templates and source-verification headers that cross-check referenced paths, exports, and configs. This enforces strict freshness rules and stops hallucinated docs during on-demand generation.

What is source verification for architecture documentation?▼

Source verification for architecture documentation is a compliance protocol requiring a standardized header and checklist. It cross-checks referenced source paths, exports, and environment usage to eliminate hallucinated information in generated docs.

How do I generate CLI and deployment docs on demand without hallucinations?▼

Generate CLI and deployment docs on demand by triggering the `/docs new` workflow with selected reference templates. The process enforces source-verification guardrails and freshness rules to ensure output accuracy and prevent hallucinated information.

Does graph metadata support traceability for generated documentation?▼

Yes, graph metadata supports traceability for generated documentation. When `.beads/graph/` exists, the documentation workflow optionally integrates graph-aware behavior to anchor tracing and detect stale docs.

What are the limitations of using templates for agent-generated docs?▼

Template-based agent-generated docs require strict YAML-defined skill discovery and compliance with verification headers. Without optional graph metadata in `.beads/graph/`, advanced traceability and automated stale-doc detection features remain unavailable.