write-document

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.

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.

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.

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.

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.