What problem does it solve?
This skill owns ONLY the docs-specific middle of the bead lifecycle, ensuring that the documentation associated with code changes is accurate, well-structured, and aligned with the bead's voice and decisions. The deliverable is a tracked file in the repo (e.g., README.md or a docs folder entry), not an internal memory artifact.
Core Features & Use Cases
- Provides the docs-focused middle (gap identification, voice sampling, drafting, and code-aligned review) while deferring lifecycle scaffolding to bead-lifecycle-shell.
- Supports explicit invocation or router-driven activation to produce well-formed, code-validated documentation across doc-only and doc-as-a-bead scenarios.
- Ensures the produced doc matches code references, is runnable where applicable, and surfaces only necessary decisions via optional overhead.
Quick Start
Invoke docs-a-bead with a target document (e.g., update README) to begin drafting and reviewing a tracked doc against code.