What problem does it solve? Writing architecture design documents and test plans for a Kubernetes operator requires grounding every claim in real Go types, controllers, and test files, and keeping the two documents consistent with each other and with the code. This Skill enforces that discipline so design docs stay accurate, reviewable, and traceable instead of drifting into stale prose. ## Core Features & Use Cases - Grounded design authoring: Researches the actual codebase (CRDs in operator/api/v1alpha1/, reconcilers, webapi endpoints, existing tests) before drafting, then writes a numbered design doc following house templates with real Go structs, YAML examples, state machines, and observability tables. - Companion test plan generation: Produces a test plan with permanent scenario IDs (U-, I-, E-, M-), Positive/Negative/Boundary/Regression typing, axis coverage tables, and an honest gap list, with every test function name verified by grep. - Quality gates and conventions: Runs the house-style quality gate and the CRD checker script over the documents, enforces appendix-based full type declarations, and manages cross-linking between design, test plan, and work plan documents. - Use Case: When a GitHub issue asks for a new storage feature, use this Skill to produce design-<slug>.md and test-plan-<slug>.md that cite real code, pass all style gates, and are ready for review. ## Quick Start Ask the assistant to write a design document and test plan for a specific operator feature or GitHub issue, for example: "Write a design doc and test plan for issue #142 covering volume snapshot scheduling."
