doc-coauthoring

You can co-author structured technical documents like ADRs and design docs by answering 3–5 focused interview questions. The Skill then generates a complete document using a predefined template, ensuring consistent structure and language across your engineering team.

The best way to create a postmortem or runbook is using a prompt-driven interview that collects purpose, audience, and scope before drafting. This guardrail approach ensures the final templated output captures all necessary operational context.

Yes, you can generate an RFC or onboarding guide without starting from scratch. The Skill guides you through a focused interview and automatically outputs a complete document in the corresponding template, eliminating the blank page problem.

The guided interview approach works for ADRs, design docs, runbooks, postmortems, onboarding guides, and RFCs. It enforces a prompt-driven interview with 3–5 questions for each document type to ensure comprehensive coverage.

To ensure consistent structure across technical documents, use template-based output driven by a guided interview. By capturing the document's purpose upfront and applying standardized templates, the Skill maintains uniform language and formatting across all generated docs.

Before co-authoring a technical document, you need to define its purpose, audience, and scope. The Skill enforces these guardrails during the interview phase to ensure the generated template output meets your team's specific requirements.