ada-continuous-phased-delivery

Executes approved multi-phase implementation plans with per-phase verification, independent review, and Git discipline.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-continuous-phased-delivery-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-continuous-phased-delivery
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-continuous-phased-delivery
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-continuous-phased-delivery-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Approved multi-phase implementation plans often stall on constant confirmation prompts or, worse, run unchecked without verification, review, or recoverable checkpoints. This Skill drives continuous autonomous execution through bounded phases while enforcing authorization envelopes, evidence-based gates, and explicit stop conditions. ## Core Features & Use Cases - Authorization Envelope & Phase Loop: Records goal, scope, mutations, exclusions, gates, and escalation rules before editing, then runs one bounded phase at a time with baseline checks, focused verification, and coherent commits. - Independent Batch Audit Gate: Performs read-only audits of a batch of changes against a numbered checklist, producing PASS/FAIL verdicts backed by file:line evidence and re-run tool output. - Review-Gated Batch Loop: Supports pre-implementation review with explicit user approval per batch, including canonical verification chains (build, test, diff check) and real-browser acceptance testing. - Use Case: A user approves a five-phase refactoring plan and asks the agent to implement, test, review, and open a PR without routine check-ins — the Skill continues automatically through green phases but stops immediately on credential prompts, destructive migrations, or scope expansion. ## Quick Start Tell the agent to execute the already-approved implementation plan continuously phase by phase, verifying and committing each green phase and stopping only for new decisions or unsafe side effects.

Frequently Asked Questions about ada-continuous-phased-delivery

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

FAQPage Schema
How do I run an approved implementation plan continuously without confirming every step?

Approve the plan explicitly, then invoke continuous phased delivery. The agent records an authorization envelope, executes one bounded phase at a time, verifies each phase gate, and continues automatically only while evidence stays green and no new decisions arise.

How do I audit a batch of code changes against a checklist?

Use the batch audit gate with a numbered checklist. It performs a read-only review, re-runs tests and generators for evidence, and reports PASS or FAIL per item with file:line citations, never modifying the worktree.

When should I not use continuous phased delivery?

Avoid it during discovery or planning, when requirements are ambiguous, when the user wants review after every phase, or when work involves credentials, releases, destructive migrations, or other unapproved side effects. Single focused edits do not need phased orchestration.

What stop conditions halt autonomous phase execution?

Execution stops when evidence contradicts the plan, scope must expand materially, a gate fails repeatedly without a root cause, user changes conflict, or secrets, destructive operations, missing merge authority, or unavailable dependencies appear.

Does continuous execution include Git commits and pull requests?

Only when Git delivery is explicitly authorized. It then creates a named work branch, makes coherent buildable commits, re-runs gates before each commit, pushes only the work branch, and opens a PR with scope, evidence, risks, and AI disclosure.