write-document

Guide structured technical document creation from briefs and save Markdown to .output/docs.

Updated Aug 27, 2026

Search Tags:#workflow #documentation #onboarding #adr #api-reference #write

Ready to run

npx skills add https://github.com/igot-ai/os-twin --skill write-document

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-document
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/narrative-designer/write-document
Command: npx skills add https://github.com/igot-ai/os-twin --skill write-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams produce consistent, high-quality technical documentation through guided conversation, reducing manual drafting time.

Core Features & Use Cases

Guided document planning for ADRs, feature specs, API references, onboarding guides.
Automatic frontmatter and document structure enforcement to ensure consistency.
Output saved to .output/docs with an integrated review workflow.

Quick Start

Provide a brief for your document type and audience, and the assistant will generate a structured Markdown document saved to .output/docs/.

Frequently Asked Questions about write-document

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

FAQPage Schema

How do I generate structured technical documentation from a brief?▼

To generate structured technical documentation from a brief, this Skill uses a guided conversation to plan and draft the content. It automatically enforces document structure and frontmatter, outputting the final Markdown file for review.

What is the best way to write an Architecture Decision Record automatically?▼

Writing an Architecture Decision Record (ADR) is best handled through this guided workflow, which structures your technical decisions into a consistent Markdown format. The output is automatically saved to the .output/docs directory for immediate review.

Can I use this to create API references and onboarding guides?▼

Yes, you can create API references and onboarding guides. The workflow applies its enforced document structure and frontmatter rules to these specific documentation scenarios, ensuring your technical content remains consistent across different document types.

How does guided conversation help draft feature specs?▼

Guided conversation helps draft feature specs by interactively extracting requirements from your initial brief. This process ensures the resulting document enforces strict frontmatter and structural consistency before automatically saving it to .output/docs.

Are there limitations to what this technical documentation workflow can do?▼

A limitation of this technical documentation workflow is that it requires an initial brief and relies on guided conversation. It focuses on generating structured Markdown files saved to .output/docs rather than handling freeform or unstructured drafting tasks.