7. Writing & Documentation

Generates clear API authentication documentation with OAuth 2.0 flows, token management procedures, and security best practices using visual diagrams.

Generates multilingual blog posts from structured interviews about Intent-Driven Development adoption, documenting experiences, lessons, and best practices.

Enables structured documentation following DITA and topic-based principles, separating content into tasks, concepts, and references for reuse and clarity.

Creates efficient troubleshooting guides with diagnostic flows and problem classification to improve user self-resolution.

Syncs finalized development details including interfaces, data structures, and architecture decisions to Intent after successful implementation and user confirmation.

Provides a specification search interface for AIWorkflowOrchestrator, enabling quick access to architecture, API, and security requirements via keyword search in the references directory.

Automates creation of new AI agent skills by generating specifications and documenting patterns per the Agent Skills framework.

Manages document versioning using Git with branch strategies, commit conventions, and automated changelogs for technical documentation.

Provides methodology for classifying and defining functional/non-functional requirements using ISO 25010, SMART criteria, and industry standards to ensure completeness and measurability.

Enables secure publication and configuration of OpenAPI documentation using Swagger UI, supporting static HTML, React, and Next.js integrations.

Creates clear, user-focused documentation by aligning content with reader needs and understanding levels, applying plain language guidelines.

Generates structured, readable outputs in Markdown, JSON, YAML, and table formats for technical documentation and code clarity.

Creates executable task specification documents by decomposing complex development tasks into 13 phases using software engineering principles.

Designs user-friendly document structures for efficient information retrieval, emphasizing hierarchy, navigation, and content organization in technical documentation.

Provides structured patterns for documenting API errors, troubleshooting guides, and runbooks to enhance developer experience and reduce support overhead.

Provides templates and guidelines for crafting clear Product Requirement Documents (PRD) to align business objectives with technical development.

Creates structured, standards-compliant requirement documents (SRS) using Karl Wiegers methodology and IEEE 830, ensuring clarity for stakeholders and developers.

Automates updating multilingual documentation including README files and store descriptions across all language versions.

Creates bilingual (zh-TW/en) release notes in Markdown format for GitHub releases, automating multilingual documentation.

Converts ambiguous instructions into clear, specific, and measurable steps with defined success criteria, enhancing comprehension and execution.

Converts tacit organizational knowledge into structured, reusable documentation via SECI model and best practices.

A guide for creating and updating Claude skills with specialized knowledge, workflows, and tool integrations.

Creates structured Product Requirements Documents (PRDs) with acceptance criteria for feature planning, migrations, and refactors.

Standardizes OpenWork patch release notes and GitHub release documentation for consistency and clarity.