technical-writing

You can generate complete API documentation by providing markdown inputs and optional reference files. The skill processes these to produce structured, scannable API references ready for publishing.

Writing architecture decision records is best handled using unified templates for structure and audience guidance. This ensures clarity and completeness for engineering teams reviewing architectural choices.

Yes, you can create runbooks and tutorials using the same unified templates. The skill provides guidance on structure and review checklists to ensure operational accuracy and onboarding clarity.

You do not need reference files to produce structured technical docs, but they are optional. Providing reference files enables the skill to include detailed examples in the final markdown output.

To write ADRs that are clear and easy to navigate, use structured templates with review checklists. This approach ensures your architecture decision records maintain consistency and completeness across the project.

The technical documentation generation skill outputs ready-to-publish markdown documents. It takes markdown inputs and optional reference files to produce structured, scannable technical documentation.