templates

Generate plan, spec, design note, and task documents from canonical templates.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill templates-grimlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: templates
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/templates
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill templates-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents inconsistent, memory-based document structure by ensuring you always start from the repository’s canonical templates.

Core Features & Use Cases

  • Canonical workflow documents: Provides ready-made structures for plans, feature specs, refactor adaptation plans, design notes, and task tracking.
  • Structure-first guidance: Enforces that templates define layout only, while population rules come from the requesting workflow skill.
  • Language-aware spec scaffolding: References language-specific feature spec patterns so test/spec sections match the target ecosystem.

Quick Start

Use the templates skill to create a new plan or spec by copying the appropriate template from references into the target .copilot path and filling all placeholders.

Frequently Asked Questions about templates

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

FAQPage Schema
How do I generate consistent feature specs and design notes for my development workflow?

To generate consistent feature specs and design notes, you should use canonical templates rather than relying on memory. This ensures your development workflow documents maintain a standardized structure with predefined sections and placeholder fields.

Why does my documentation structure change every time I plan a new feature?

Your documentation structure changes because it is being reproduced from memory instead of canonical templates. Starting from standardized plan and spec templates prevents inconsistent layouts and ensures all required sections are present.

How do I create language-aware feature spec scaffolding for my project?

You create language-aware feature spec scaffolding by selecting a matching language-specific spec reference from your template repository. This ensures the test and spec sections match your target ecosystem's specific patterns.

What is the best way to standardize refactor adaptation plans and audit passes?

The best way to standardize refactor adaptation plans and audit passes is to copy the appropriate canonical template into your target path. You then fill all angle bracket placeholders while following the requesting workflow skill's population rules.

Do I need any external dependencies to use these documentation templates?

No external dependencies are required to use these documentation templates. You simply read the relevant template file from your references directory, copy it into the target path, and fill in the placeholders to complete your workflow documents.

Can I use these templates to scaffold task tracking and architecture notes?

Yes, you can use these templates to scaffold task tracking and architecture notes. They provide ready-made structures for plans, feature specs, refactor adaptation plans, design notes, and task tracking documents.