What problem does it solve? Multi-scope feature work in the Bubbles framework fails lint and state-transition gates when scope files use the wrong layout, mismatched Test Plan and Definition-of-Done rows, or violated isolation rules. This Skill encodes the exact conventions so scope artifacts pass state-transition-guard.sh and artifact-lint.sh on the first attempt. ## Core Features & Use Cases - Layout and DoD Decisions: Choose between a single scopes.md file (≤5 scopes) and per-scope directories (6+ scopes), and between single-file and tiered DoD formats. - Test Plan / DoD Parity Enforcement: Ensures Test Plan row counts match DoD test items, includes stress-test rows when latency SLAs exist, and applies the v4.1.0 scope-kind taxonomy (runtime-behavior, contract-only, deploy-pointer, and others) to control E2E enforcement. - DAG-Based Work Selection: Picks the next scope by dependency readiness, enforces per-scope isolation, and surfaces pre-existing bugs before starting new work. - Use Case: When splitting a feature into eight scopes, use this Skill to create specs/<NNN>/scopes/_index.md plus per-scope directories with valid Gherkin scenarios, Test Plans, and tiered DoD sections that pass artifact lint. ## Quick Start Ask the agent to create the scopes for a new feature in specs/ following the Bubbles scope workflow rules, including the Test Plan and tiered Definition of Done.
