cauto

Orchestrate the implementation pipeline from spec through QA to PR creation.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill cauto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cauto
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cauto
Command: npx skills add https://github.com/joshft/correctless --skill cauto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the full end-to-end implementation pipeline after a human-approved spec review, ensuring safe phase transitions, separation of responsibilities, and auditable governance across spec, TDD, implementation, QA, and verification.

Core Features & Use Cases

  • Orchestrates sequential pipeline steps (ctdd, simplify, cverify, cupdate-arch, cdocs) and PR creation, enforcing phase gates and dependency boundaries.
  • Maintains an auditable trail of skill invocations, outcomes, and escalation events, with automatic resumption and error handling.
  • Supports intensity-aware behavior and preference-driven decisions, while delegating deterministic choices to the policy tier and human intervention when needed.
  • Use Case: A project starts with an approved spec; /cauto manages the full workflow from TDD to PR, consolidating artifacts and generating a summary report.

Quick Start

Start the end-to-end workflow by triggering /cauto on a feature branch after spec approval, allowing the orchestrator to drive the pipeline.

Frequently Asked Questions about cauto

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

FAQPage Schema
How do I automate the software implementation pipeline after spec approval?

To automate the implementation pipeline after spec approval, use an orchestrator to enforce sequential phase transitions across TDD, implementation, QA, and verification. It coordinates each breakout step in order, ensuring deterministic phase gates and optional PR creation.

What is an automated workflow orchestrator with deterministic phase gates?

An automated workflow orchestrator with deterministic phase gates coordinates the full implementation pipeline by enforcing strict separation between spec, test, implementation, QA, and verification. It maintains auditable trails of skill invocations and handles escalations automatically.

How do I maintain an auditable trail for QA and TDD workflow phases?

To maintain an auditable trail for QA and TDD workflow phases, the orchestrator logs skill invocations, outcomes, and escalation events during the pipeline. This ensures governance and supports automatic resumption and error handling across phases.

Can I enforce strict separation of spec, test, and implementation in my pipeline?

Yes, you can enforce strict separation of spec, test, and implementation in your pipeline. The orchestrator applies deterministic phase gates between these stages, ensuring safe transitions and auditable governance throughout the end-to-end workflow.

Does the pipeline orchestrator support automatic error handling and resumption?

The pipeline orchestrator supports automatic error handling and resumption by maintaining an auditable trail of outcomes and escalation events. It manages phase progression safely, delegating deterministic choices to the policy tier or human intervention when needed.

When should I use an automated pipeline orchestrator for software projects?

You should use an automated pipeline orchestrator for software projects requiring strict separation of spec, test, implementation, QA, and verification. It is ideal when you need auditable governance, deterministic phase gates, and optional PR creation after human-approved specs.