cmd-workflow

Automating end-to-end repository delivery involves generating a TASK_CONTRACT to define scope, creating a QUALITY_PROFILE for risk-based TDD, and producing a REVIEW_PACKET. This workflow orchestrates changes from intake to handoff using a deterministic loop to converge on a verified build.

A task contract is a formal artifact that specifies scope and acceptance criteria for repository changes. You need one when your team requires a structured, auditable process for code delivery to reduce review cycles and ensure correctness from intake through handoff.

Generating a review packet requires running the end-to-end delivery workflow through its Architect, Builder, and Critic loop. The process automatically compiles behavior diffs and verification evidence into a REVIEW_PACKET to speed up developer review.

Yes, risk-based TDD is supported by mapping quality checks to verification commands within a generated QUALITY_PROFILE. This approach executes tests against formal task contracts and performs gate verifications using included templates to ensure build correctness.

Automated repo delivery is designed specifically for teams needing structured handoff and auditable artifacts. It produces formal TASK_CONTRACT, QUALITY_PROFILE, and REVIEW_PACKET documents while running gate verifications to minimize disruption during the review cycle.

Automating repo delivery with task contracts requires providing explicit task requests and constraints to initiate the workflow. This structured approach is suited for formal, auditable processes and may be unnecessary for simple changes that do not require risk-based test strategies or review packets.