write-documents

Generate API documentation by providing a ticket or project brief to automate structured Markdown content creation. The workflow applies consistent UI terminology and performs textlint checks to ensure high-quality Japanese technical writing across APIs, features, and user guides.

The best way to write feature specifications and user guides is using an automated workflow that loads project knowledge, generates Markdown body structures with YAML frontmatter, and validates Japanese language quality via textlint checks for consistent UI terminology.

Automated technical writing handles Markdown structure by fulfilling YAML frontmatter in SKILL.md files and generating a structured Markdown body. It performs textlint checks end-to-end to validate content quality and Japanese writing conventions.

Yes, you can use this documentation generation approach for user manuals and onboarding materials. It automates clear technical documentation creation with an emphasis on UI terminology consistency and high-quality Japanese writing polish.

Yes, you need to provide a ticket or project brief as input. The automated workflow then loads your project knowledge to generate polished technical documentation, including API docs, feature specifications, and user manuals, following the required structure.