docs-agile-integration

• SKILL.mdcore · 3,422 bytes
• guidelines.mddoc · 2,203 bytes
• references/core/knowledge.mddoc · 6,485 bytes
• workflows/define-docs-done.mddoc · 2,908 bytes
• workflows/integrate-docs-agile.mddoc · 3,054 bytes

# Docs Agile Integration

Use this skill to integrate documentation with Agile product development without hiding docs-specific work. It helps writers and product teams plan docs, reviews, release readiness, and maintenance in the cadence where product decisions happen.

This skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 2, "Agile," Chapter 19, "Working with Engineers," Chapter 22, "Working with Product Management," and Chapter 23, "Working on a Remote Team." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6

## Quick Start

1. Load `guidelines.md` to choose the smallest useful reference set.
2. Identify the team's Agile cadence, planning artifacts, release model, and where docs are currently invisible.
3. Use `workflows/integrate-docs-agile.md` to attach docs work to product work.
4. Use `workflows/define-docs-done.md` to add documentation checks to definition of done or release readiness.
5. Separate feature-sprint docs from docs work that legitimately spans sprints or teams.
6. Return recommended board changes, doc tasks, review checkpoints, blockers, and retrospective signals.