What problem does it solve? Code often ships without matching documentation, leaving devbook chapters missing, thin, or stale. This Skill reads an implementation and its tests, then produces a capture plan describing exactly what the chapter should say — without writing any files itself. ## Core Features & Use Cases - Six chapter kinds: Covers aggregates, domain services, features, feature flags/settings, arc42 building blocks, and design component guidelines, each with its own reading and drafting rules. - Evidence-based drafting: Extracts invariants from unit tests and requirements from e2e tests (and the running product for features), drafting SHALL sentences with scenario cases and test references. - Verdict-driven workflow: Reports aligned, code-ahead, spec-ahead, conflict, or unresolved per chapter, stopping or handing off to other flows when planning is not appropriate. - Use Case: A domain event was added to an aggregate but never documented. Run this Skill against the aggregate's chapter to receive a Markdown capture plan with ADDED/MODIFIED/REMOVED deltas ready for human review. ## Quick Start Ask the assistant to capture specs for the Order aggregate in the sales bounded context and produce a capture plan for its missing domain chapter.
