skills.rest
karstenheld3
karstenheld3COMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-documents

Generate standardized documents from predefined templates with frontmatter and required sections.

Updated Aug 27, 2026
Search Tags:#templates#documentation#writing#SPEC#INFO#STRUT
One-click install
npx skills add https://github.com/karstenheld3/SharePoint-GPT-Middleware --skill write-documents
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-documents
Source: https://github.com/karstenheld3/SharePoint-GPT-Middleware/tree/main/.windsurf/skills/write-documents
Command: npx skills add https://github.com/karstenheld3/SharePoint-GPT-Middleware --skill write-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides standardized document templates for INFO, SPEC, IMPL, TEST, FIX, FAILS, REVIEW, TASKS, and STRUT documents, ensuring consistency across projects.

Core Features & Use Cases

  • Template-driven document creation for all core document types (INFO, SPEC, IMPL, TEST, FIX, FAILS, REVIEW, TASKS, STRUT)
  • Enforces MUST-NOT-FORGET rules, unique document IDs, and consistent frontmatter
  • Cross-document referencing via Doc IDs and template references for governance and auditability
  • Supports STRUT-style planning inserts and hierarchical box-drawing structures for complex plans
  • Facilitates collaboration by providing ready-to-use scaffolds for writers, PMs, and engineers

Quick Start

  1. Describe the document you want to create (e.g., SPEC_AUTH for an authentication module)
  2. Choose the appropriate template, such as SPEC or IMPL, and open the corresponding template file
  3. Populate the frontmatter (Doc ID, Goal, Target file) and sections exactly as the template specifies
  4. Save the document and reference it from related documents by Doc IDs

Frequently Asked Questions about write-documents

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

FAQPage Schema
How do I create standardized documentation across my team?▼

Standardized documentation uses predefined templates (INFO, SPEC, IMPL, TEST, FIX, FAILS, REVIEW, TASKS, STRUT) to enforce consistent structure, frontmatter, and section formatting. This skill applies the appropriate template based on document type, assigns unique Doc IDs, and generates ready-to-use scaffolds that enforce organizational governance rules and enable cross-document referencing.

What documentation templates does this provide?▼

Nine core templates cover the full documentation lifecycle: INFO for context, SPEC for requirements, IMPL for implementation details, TEST for test plans, FIX for bug fixes, FAILS for failure analysis, REVIEW for design reviews, TASKS for project planning, and STRUT for hierarchical planning structures with box-drawing support.

How do I ensure documentation consistency across projects?▼

Templates enforce MUST-NOT-FORGET rules, consistent frontmatter structure, and required sections. Doc IDs enable cross-document referencing for auditability. Populate the frontmatter (Doc ID, Goal, Target file) exactly as the template specifies, then reference related documents by their Doc IDs to maintain governance.

Can I use these templates for collaborative writing?▼

Yes. Templates provide ready-to-use scaffolds that reduce writer friction and align contributions from PMs, engineers, and technical writers. Predefined sections and frontmatter conventions make handoffs clear and enable multiple contributors to work within a consistent framework.

What's the difference between using templates versus writing documentation from scratch?▼

Templates eliminate inconsistency, reduce rework, and embed organizational rules upfront. Writing from scratch risks missing critical sections, inconsistent formatting, and governance gaps. Templates guarantee structure, Doc ID tracking, and compliance with MUST-NOT-FORGET rules without manual enforcement.

How do I reference documentation across projects?▼

Each document receives a unique Doc ID in its frontmatter. Reference related documents by their Doc IDs to create an auditable chain across INFO, SPEC, IMPL, TEST, and other document types, enabling traceability and governance across the documentation lifecycle.

Related Skills

Explore More Content & Communication Skills→
newmoon-orgnewmoon-org

create-rule

Define and standardize coding rules for Augment Agent with frontmatter templates.

Official
Intermediate
Qiue-GQiue-G

feishu-create-doc

Create Feishu cloud documents from Lark-flavored Markdown content.

Community
Intermediate
alaminmainalaminmain

documentation-templates

Standardize READMEs, API docs, and code comments with YAML frontmatter templates.

Community
Basic
SpillwaveSolutionsSpillwaveSolutions
62

confluence

Convert Markdown to Confluence Wiki Markup and update pages via REST.

Official
Advanced