Guidelines: Skill Documents

Apply standardized documentation templates with mandatory frontmatter to tickets and reviews.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/go-go-golems/tactician --skill guidelines-skill-documents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Guidelines: Skill Documents
Source: https://github.com/go-go-golems/tactician/tree/main/ttmp/_guidelines
Command: npx skills add https://github.com/go-go-golems/tactician --skill guidelines-skill-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The guidelines provide a unified framework for creating and maintaining consistent business and engineering documents.

Core Features & Use Cases

  • Standard templates for Code Review, Design Documents, Index, Log, Playbook, Reference, Script, Task List, Tutorial, and Working Notes.
  • Proven best-practices that improve clarity, traceability, and reuse across projects.
  • Quick-start flows to apply the templates to new tickets or tasks.

Quick Start

Apply the guidelines to a new ticket by selecting the appropriate template and filling required sections.

Frequently Asked Questions about Guidelines: Skill Documents

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

FAQPage Schema
How do I standardize documentation templates for consistent project outcomes?

You standardize documentation templates by applying structured workflows with mandatory frontmatter and predefined sections for reviews, playbooks, and tasks. This enforces template verification to ensure document completeness and discovery across projects.

What types of structured documents are needed for engineering knowledge management?

Engineering knowledge management relies on standard templates for Code Review, Design Documents, Playbooks, References, and Working Notes. These formats improve clarity, traceability, and reuse across technical projects.

How do I apply documentation guidelines to a new ticket or task?

To apply documentation guidelines to a new ticket, select the appropriate template and fill in the required sections. This quick-start workflow ensures structured data capture and immediate traceability for the task.

Why enforce a frontmatter contract in markdown documentation?

Enforcing a frontmatter contract in markdown documentation ensures completeness and discovery. It standardizes the metadata required for automated processing and maintains consistency across knowledge bases and engineering documents.

Can I use these documentation workflows without prior template configuration?

You can use these workflows directly without prior configuration because the guidelines provide pre-established templates with mandatory frontmatter. This allows immediate application to new tickets, reviews, and knowledge bases.

What is the best way to maintain consistency across business and engineering documents?

The best way to maintain consistency across business and engineering documents is to use a unified framework of standard templates. This framework provides proven best-practices that improve clarity, traceability, and reuse across projects.