sdlc-orchestrate

Implements OpenSpec-backed changes through phased workspaces, child agents, and independent audits.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill sdlc-orchestrate-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-orchestrate
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/core/dependencies/sdlc/sdlc-orchestrate
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill sdlc-orchestrate-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a planned specification often requires babysitting: decomposing work, running phases, verifying each stage, and recovering from failures. This Skill autonomously executes a planned OpenSpec change end-to-end inside explicit boundaries and hard verification gates, so implementation proceeds without constant supervision. ## Core Features & Use Cases - Autonomous Phase Execution: Reads the planned OpenSpec change, decides whether to decompose it into smaller phase specs, and implements each stage in isolated git worktrees with child agents or Jules delegation. - Independent Audit Gates: Verifies every phase against the phase ledger, OpenSpec task checkboxes, and verification scripts, fixing failures autonomously within a retry budget before continuing. - State Tracking and Handoff: Maintains .sdlc/phase-ledger.md, .sdlc/run.json, and .sdlc/state.md, then prepares a local preview and hands off to sdlc-verify. - Use Case: After planning a feature that touches both frontend and backend, invoke this Skill to split the work into vertical phases, delegate implementation to Jules via GitHub issue labels, audit each phase's diff, and receive a preview URL plus the exact next verification command. ## Quick Start Use sdlc-orchestrate to implement the planned OpenSpec change for my feature and stop when it is ready for verification.

Frequently Asked Questions about sdlc-orchestrate

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

FAQPage Schema
How do I implement an OpenSpec change autonomously?▼

Run sdlc-orchestrate with the change name after planning is complete. It resolves the active change, decomposes it into phases if needed, implements each stage in an isolated worktree, audits every phase, and stops with a preview ready for sdlc-verify.

When should a change be decomposed into multiple phases?▼

Decompose when the change spans frontend and backend, involves migrations or security behavior, alters architecture or data flow, or risks breaking existing behavior. Single-phase implementation is reserved for one coherent, low-risk behavior slice provable in one verification pass.

Can I delegate implementation phases to Google Jules?▼

Yes. Well-bounded implementation phases with explicit verification criteria can be delegated to Jules by adding the jules label to the corresponding GitHub issue. Local subagents or direct execution are preferred for tiny changes, credential-dependent work, or analytical tasks.

What happens when a phase audit fails?▼

The failure is recorded in the phase ledger, and the Skill diagnoses and fixes it autonomously within a retry budget without continuing to later phases. If the budget is exhausted or a user decision is required, it stops with evidence and a precise blocker.

Does sdlc-orchestrate merge or push to main?▼

No. It never pushes to main, merges, archives, or deletes workspaces during orchestration. It stops after implementation passes all gates and instructs you to run sdlc-verify for final release and integration.