docs-agile-integration
Integrate documentation work with Agile product development by making docs visible in sprint planning, release trains, definitions of done, review timing, and retrospective improvement. Use when docs are missing from scrum boards, stories, acceptance criteria, release planning, or cross-team work, or when writers need a lightweight process for documentation inside Agile teams.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- docs-agile-integration
- license
- MIT
- metadata
- { "tags": "developer-docs,technical-writing,documentation,agile,docs-ops", "version": "0.1.0", "category": "Writing", "displayName": "Docs Agile Integration" }
- description
- Integrate documentation work with Agile product development by making docs visible in sprint planning, release trains, definitions of done, review timing, and retrospective improvement. Use when docs are missing from scrum boards, stories, acceptance criteria, release planning, or cross-team work, or when writers need a lightweight process for documentation inside Agile teams.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 4
- 参考文档guidelines.md2.2 KB
- 参考文档references/core/knowledge.md6.3 KB
- 参考文档workflows/define-docs-done.md2.8 KB
- 参考文档workflows/integrate-docs-agile.md3.0 KB
03 SKILL.md 正文
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
- Load
guidelines.mdto choose the smallest useful reference set. - Identify the team's Agile cadence, planning artifacts, release model, and where docs are currently invisible.
- Use
workflows/integrate-docs-agile.mdto attach docs work to product work. - Use
workflows/define-docs-done.mdto add documentation checks to definition of done or release readiness. - Separate feature-sprint docs from docs work that legitimately spans sprints or teams.
- Return recommended board changes, doc tasks, review checkpoints, blockers, and retrospective signals.
Default Output
When integrating docs with Agile work, return:
- Current process map - cadence, artifacts, boards, roles, release gates, and review paths.
- Docs visibility gaps - where docs impact, tasks, blockers, reviews, or release readiness are missing.
- Recommended workflow - ticket/linking model, planning checkpoints, owner, and review timing.
- Definition-of-done updates - docs impact, draft, review, QA, publish, release notes, and maintenance checks.
- Cross-sprint handling - how scenario, maintenance, IA, or cross-team docs stay visible without pretending to fit one sprint.
- Inspect-and-adapt signals - support feedback, review misses, late docs, stale content, and retrospective actions.
Contents
| Need | Start Here |
|---|---|
| Understand docs and Agile concepts | references/core/knowledge.md |
| Integrate docs into planning and boards | workflows/integrate-docs-agile.md |
| Define docs done and release readiness | workflows/define-docs-done.md |
| Route by task or symptom | guidelines.md |
Core Posture
- Treat documentation as product work.
- Make docs visible in the planning system the product team already uses.
- Match docs cadence to actual scope instead of forcing every docs activity into one sprint.
- Add lightweight checkpoints before release risk appears.
- Use retrospectives and customer signals to improve the process.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.