bubbles-dod-validation

Validates Definition of Done items against tiered checks before marking scopes complete.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-dod-validation-pkirsanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bubbles-dod-validation
Source: https://github.com/pkirsanov/bubbles/tree/main/skills/bubbles-dod-validation
Command: npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-dod-validation-pkirsanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents frequently mark work as done without real evidence, leaving broken features and fabricated test results. This Skill enforces a two-tier validation checklist so a scope can only transition to Done when every Definition of Done item carries captured proof. ## Core Features & Use Cases - Tier 1 Universal Checks: Verifies all DoD checkboxes are checked, each with inline evidence of at least 10 lines of raw output, plus test plan parity, test file existence, zero warnings, and zero TODO/FIXME markers. - Tier 2 Role-Specific Profiles: Loads role-matched validation rules for implement, test, validate, audit, docs, and bug agents, such as adversarial regression tests for bug fixes. - Mode Ceiling Pre-Flight: Checks the workflow mode status ceiling before any non-spec file edit and returns a route_required result when the ceiling forbids the change. - Use Case: Before flipping a scope status to Done or emitting a completed_owned result envelope, run this validation to confirm every DoD item has genuine captured evidence rather than narrative claims. ## Quick Start Validate whether the current scope's Definition of Done items all pass the Tier 1 and Tier 2 checks before marking it Done.

Frequently Asked Questions about bubbles-dod-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Definition of Done before marking a scope complete?▼

Run the Tier 1 universal checks in order: confirm all DoD checkboxes are checked, each has an inline evidence block of at least 10 lines, the test plan maps to DoD items, and no TODO or FIXME markers remain. Then apply the Tier 2 role-specific profile for the agent.

What evidence is required for a DoD item to be checked?▼

Each checked DoD item must carry its own evidence block with at least 10 lines of raw captured output, such as real exit codes and test counts. A narrative claim like all tests pass without terminal output is rejected as fabrication.

What is the difference between Tier 1 and Tier 2 validation checks?▼

Tier 1 contains nine universal checks every agent and scope must pass, covering evidence, test parity, and zero warnings. Tier 2 loads role-specific rules from validation-profiles.md, such as Gherkin coverage for test agents or reproduction evidence for bug agents.

When does the mode ceiling block a scope from completion?▼

Gate G073 checks state.json workflowMode against the statusCeiling in modes.yaml before any non-spec file edit. If the ceiling forbids the required edit, the skill returns route_required instead of rationalizing an exception.

Can a spec be marked done if one scope is still in progress?▼

No. Gate G024 requires all scopes of a spec to be Done with zero in-progress or blocked items before the spec itself can be marked done. Each scope in turn requires all DoD items checked with validated evidence.