How do I install the Doc Templates skill?

Run npx skillmds@latest add app-builders-club/doc-templates in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doc Templates safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doc Templates?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doc Templates free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doc Templates?

app-builders-club (@app-builders-club) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doc Templates by app-builders-club — Agent Skill

Name: Doc Templates
Author: app-builders-club

Doc Templates

Canonical templates for every MVP Builder pipeline artifact. Use whenever generating, regenerating, or restructuring any ai-docs artifact — spec.md, FEATURES.md, ux.md, ui.md, plan.md, tasks.md, validation checklists, resolutions.md, feedback.md, design-system.md — so the exact section structure downstream agents parse is preserved. Triggers on: generate spec, create feature docs, write tasks, validation checklist, review feedback, design setup, artifact template.

File contents

Document Templates

Single source of truth for pipeline artifact structure. Every artifact the pipeline produces follows its template exactly — downstream agents parse these structures by section name and ID convention (FR-XXX, TEST-XXX, CHK###, REV-XXX), so a missing or renamed section breaks the chain, not just the style.

Usage

Pick the template for the artifact you are about to generate (table below).
Read it from references/ at the stage start — not all templates upfront.
Fill every section. Never invent, rename, or drop sections. Placeholders in [BRACKETS] are replaced; MODEL INSTRUCTION blocks guide filling and are removed from output.

Template Index

Template	Produces	Primary consumer
`references/spec-template.md`	`ai-docs/features/[name]/spec.md`	`/feature`, `/clarify`
`references/features-template.md`	`ai-docs/FEATURES.md`	`/feature`
`references/ux-template.md`	`ai-docs/features/[name]/ux.md`	feature-docs agent
`references/ui-template.md`	`ai-docs/features/[name]/ui.md`	feature-docs agent
`references/plan-template.md`	`ai-docs/features/[name]/plan.md`	feature-docs agent
`references/tasks-template.md`	`ai-docs/features/[name]/tasks.md`	feature-docs agent
`references/checklist-template.md`	`ai-docs/features/[name]/validation/[domain]-checklist.md`	`/validation`
`references/resolutions-template.md`	`ai-docs/features/[name]/validation/resolutions.md`	`/validation`
`references/feedback-template.md`	`ai-docs/features/[name]/feedback.md`	feature-review agent
`references/design-setup-template.md`	`ai-docs/references/design-system.md`, `style-guide.md`	design-setup agent

Rules

Template structure is a contract: traceability IDs defined here are referenced across spec → tasks → validation → feedback. Keep ID formats intact.
When an artifact is regenerated, regenerate from the template — never by mutating the previous artifact's structure.
Existing artifacts with the old structure are updated in place only for content, never restructured mid-feature.

---name: doc-templatesdescription: Canonical templates for every MVP Builder pipeline artifact. Use whenever generating, regenerating, or restructuring any ai-docs artifact — spec.md, FEATURES.md, ux.md, ui.md, plan.md, tasks.md, validation checklists, resolutions.md, feedback.md, design-system.md — so the exact section structure downstream agents parse is preserved. Triggers on: generate spec, create feature docs, write tasks, validation checklist, review feedback, design setup, artifact template.---# Document TemplatesSingle source of truth for pipeline artifact structure. Every artifact the pipelineproduces follows its template exactly — downstream agents parse these structures bysection name and ID convention (FR-XXX, TEST-XXX, CHK###, REV-XXX), so a missing orrenamed section breaks the chain, not just the style.## Usage1. Pick the template for the artifact you are about to generate (table below).2. Read it from `references/` **at the stage start** — not all templates upfront.3. Fill every section. Never invent, rename, or drop sections. Placeholders in `[BRACKETS]` are replaced; `MODEL INSTRUCTION` blocks guide filling and are removed from output.## Template Index| Template | Produces | Primary consumer ||----------|----------|------------------|| `references/spec-template.md` | `ai-docs/features/[name]/spec.md` | `/feature`, `/clarify` || `references/features-template.md` | `ai-docs/FEATURES.md` | `/feature` || `references/ux-template.md` | `ai-docs/features/[name]/ux.md` | feature-docs agent || `references/ui-template.md` | `ai-docs/features/[name]/ui.md` | feature-docs agent || `references/plan-template.md` | `ai-docs/features/[name]/plan.md` | feature-docs agent || `references/tasks-template.md` | `ai-docs/features/[name]/tasks.md` | feature-docs agent || `references/checklist-template.md` | `ai-docs/features/[name]/validation/[domain]-checklist.md` | `/validation` || `references/resolutions-template.md` | `ai-docs/features/[name]/validation/resolutions.md` | `/validation` || `references/feedback-template.md` | `ai-docs/features/[name]/feedback.md` | feature-review agent || `references/design-setup-template.md` | `ai-docs/references/design-system.md`, `style-guide.md` | design-setup agent |## Rules- Template structure is a contract: traceability IDs defined here are referenced across spec → tasks → validation → feedback. Keep ID formats intact.- When an artifact is regenerated, regenerate from the template — never by mutating the previous artifact's structure.- Existing artifacts with the old structure are updated in place only for content, never restructured mid-feature.

Frequently asked questions