implement-qc-loop

Automates iterative Implement and QC loops with artifact validation and guardrails.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill implement-qc-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-qc-loop
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/implement-qc-loop
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill implement-qc-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an automated, end-to-end loop that orchestrates the Implement and QC sub-skills, eliminating manual handoffs and ensuring continuous verification of development work.

Core Features & Use Cases

  • End-to-end orchestration: Runs Implement and QC in a single continuous turn, with gating and safety checks.
  • Guardrail enforcement: Enforces a maximum of 10 iterations and validates artifacts across iterations to prevent drift.
  • Artifact validation: Requires and validates .completed, qc-passed, and qc-report.md states, and reconciles tasks.md for unchecked work.
  • Workflow integration: Reads and coordinates with spec.md, plan.md, and tasks.md to maintain alignment with feature scope.

Quick Start

Trigger the loop to repeatedly run Implement then QC until QC passes or the safety limit is reached.

Frequently Asked Questions about implement-qc-loop

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

FAQPage Schema
How do I automate continuous implementation and quality assurance loops for feature development?

Automating continuous implementation and quality assurance loops is achieved by orchestrating sub-skills in an end-to-end loop that runs development and verification iteratively with safety checks until quality control passes.

What guardrails prevent infinite loops during automated QC workflow automation?

Automated QC workflow automation enforces a maximum of 10 iterations and validates artifacts across iterations to detect state mismatches and prevent drift, ensuring the loop terminates safely.

How do spec.md, plan.md, and tasks.md files integrate with an automated QC loop?

Spec.md, plan.md, and tasks.md integrate with the QC loop by acting as gating checks that maintain alignment with feature scope, while tasks.md is reconciled for unchecked work across iterations.

What artifacts are required to validate state and ensure QC reliability in a continuous loop?

Validating state and ensuring QC reliability requires .completed, qc-passed, and qc-report.md artifacts, which are checked across iterations to verify that implementation work meets quality standards.

When should I use an end-to-end Implement to QC loop instead of manual development handoffs?

An end-to-end Implement to QC loop is used when feature development pipelines require iterative implementation and verification with guardrails, eliminating manual handoffs and ensuring continuous artifact validation.