construction

Execute approved plans with TDD, audits, and gated commits.

8|Updated Jun 18, 2026

Search Tags:#tdd #software engineering #implementation #execution planning #code audit #git commits #adversarial validation

Ready to run

npx skills add https://github.com/ddobrin/plan-skills --skill construction-ddobrin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: construction
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/orchestrator/skills/construction
Command: npx skills add https://github.com/ddobrin/plan-skills --skill construction-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an approved specification and execution plan into verified, production-ready code while preventing untested, unaudited, or unauthorized changes from being committed.

Core Features & Use Cases

Execution Group Delivery: Coordinates engineer, simplifier, auditor, and implementation-validator roles for each execution group.
TDD and Validation Gates: Requires tests, auditing, adversarial diff review, persisted validation results, and explicit human approval before commits.
Use Case: When a plan contains unchecked tasks, use this Skill to implement each group sequentially, resolve failures, validate the resulting diff, and commit only approved work.

Quick Start

Use the construction skill to execute the next unchecked group in the approved plan, run its full implementation and validation workflow, and prepare it for human-approved commit.

Frequently Asked Questions about construction

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

FAQPage Schema

How do I implement an approved execution plan with TDD and gated commits?▼

To implement an approved execution plan with TDD and gated commits, the Skill coordinates development, refinement, auditing, and adversarial validation for each execution group sequentially. It enforces tests, auditing, and explicit human approval before producing one verified commit per group.

What is the best way to enforce code audits and adversarial validation before a git commit?▼

The best way to enforce code audits and adversarial validation before a git commit is using a specification-driven workflow that gates commits. This Skill requires passing audits, persisted implementation validation results, and adversarial diff review before generating an authorized commit.

How do I handle unchecked tasks in a specification-driven feature plan?▼

To handle unchecked tasks in a specification-driven feature plan, the Skill processes each execution group sequentially. It resolves failures, validates the resulting diff, and prepares the completed work for human-approved commit, ensuring no untested or unaudited changes proceed.

Do I need explicit human approval for every execution group in TDD development?▼

Yes, explicit human approval is required for every execution group in TDD development using this approach. The workflow mandates human approval alongside passing tests, code audits, and persisted implementation validation before generating a single verified commit per group.

Can I use this gated commit workflow for bug fixes and refactors?▼

Yes, you can use this gated commit workflow for bug fixes and refactors, as well as specification-driven feature work. The execution groups organize all these task types through the same TDD, adversarial validation, and auditing gates before committing.

Why does adversarial diff review prevent untested code from being committed?▼

Adversarial diff review prevents untested code from being committed by acting as a validation gate within the execution group workflow. It requires persisted implementation validation results and explicit human approval before authorizing any verified commit, blocking unauthorized changes.