Orchestrate test-first implementation workflows with ordered waves and quality gates.
npx skills add https://github.com/azigler/dotfiles --skill agents-skills-impl
Please help me install this Agent Skill. Skill: agents/skills/impl Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/impl Command: npx skills add https://github.com/azigler/dotfiles --skill agents-skills-impl
This Skill solves the coordination problem of implementing software in a test-first way while preventing implementation agents from rewriting tests or shipping unverified, stubbed, or non-composed code.
Use the agents/skills/impl skill to run an orchestrated workflow that verifies /spec readiness, dispatches /test first, then dispatches /impl, and only merges after scrutinize, checks, and stub/composition audits pass.
High-intent search queries and answers about installing and using this skill.
Test-first implementation orchestration enforces strict wave ordering by dispatching test beads first, completing and merging them, then dispatching impl beads with strict 'do not modify tests' rules to preserve test integrity.
A quality gate in test-first development is a mandatory checkpoint that runs adversarial scrutinize checks, executes automated tests, performs stub-body auditing, and validates user-facing UI or CLI composition before allowing code to merge.
To prevent stubbed code from passing, this orchestration workflow performs a mandatory stub-body audit alongside automated checks and an adversarial scrutinize gate, ensuring no unverified or incomplete implementations ship.
Yes, subsystem-based development creates dependency-typed beads for each subsystem, enforcing that test work is completed and merged on the feature branch before implementation dispatch begins.
Implementation readiness verification checks that the spec bead's 'Implementation Readiness' notes are present and unblocked, ensuring all preconditions are met before test and implementation waves are dispatched.
Validating user-facing UI and CLI composition is handled by a mandatory quality gate that verifies composed artifacts, ensuring the implemented code correctly integrates into the final user-facing interface before merging.
aziglerResolve spec bead open questions, conflicts, and dependencies with decisions.
Clawdi-AIMerge GitHub pull requests via squash after validating checks and branch status.
fkbertholdCoordinate feature-bead work with contract-driven variable middle and lifecycle scaffolding.
robotijnRun tests, lint, type checks, and security scans in parallel locally and in CI.
