12-DOCS-write

You can generate technical documentation and acceptance criteria by providing a docs-outline.md blueprint and code artifacts. The skill writes developer-focused API references, inline JSDoc, and client-facing how-to guides directly into the plan file and source files.

Yes, inline JSDoc is written directly into your source files to document non-obvious code behavior. The skill consumes your code artifacts and plan file to generate developer-focused documentation alongside the standard reference materials.

Creating role-based acceptance criteria checklists is best handled by generating detailed, testable verification steps from a docs-outline.md blueprint. This ensures all feature aspects are clearly defined and verifiable for each specific testing role.

Yes, it produces both developer documentation like API references and ADRs, alongside client-facing materials such as feature overviews. The client-facing content uses clear, jargon-free language while developer docs focus on technical implementation details.

Yes, you need a docs-outline.md blueprint discovered beforehand to write documentation and acceptance criteria. The skill consumes this plan file along with code artifacts to produce comprehensive, verifiable feature documentation.

Writing documentation and acceptance criteria together ensures all aspects of a feature are clearly defined and verifiable in one pass. Generating role-based checklists alongside API references and user guides keeps testing aligned with documented behavior.