Problem
aidd-orchestrator:01-sdlc currently exposes only an autonomous delivery contract. Teams also need a supervised path for decisions that should remain human-owned without manually interrupting the pipeline.
Product decision
Reintroduce an optional interactive mode. Autonomous mode remains the default.
This deliberately revisits the single autonomous contract introduced by #517. It is not a regression to the former behavior: the new mode adds a small number of decision gates while keeping internal implementation and repair loops autonomous.
Modes
- Autonomous: current behavior remains unchanged.
- Interactive: selected explicitly through user intent, for example “run the SDLC interactively”; no dedicated CLI flag is required.
Interactive gates
- Contract gate: after Frame produces the delivery contract.
- Plan gate: after
aidd-dev:01-plan produces or revises the implementation plan. Reuse that skill’s approval point; do not add a duplicate gate.
- Final evidence gate: after Check and applicable QA clear, before creating the draft pull request.
At each gate, present the artifact, material risks, the pending decision, and the next stage.
A rejection sends the feedback back to the artifact owner, then presents the revised gate again. Approved artifacts are resumed without regeneration. Telemetry must represent pauses and resumptions.
Acceptance criteria
- Explicit interactive intent selects interactive mode.
- No explicit mode keeps the current autonomous behavior.
- Interactive mode pauses only at the three defined gates.
- Rejected artifacts are revised by their owning stage and presented again.
- Approved artifacts are reused when the pipeline resumes.
- Implementation, test, review-repair, and QA-repair loops remain autonomous between gates.
- The final gate occurs before draft pull request creation.
- Existing autonomous SDLC tests remain green and interactive-mode coverage is added.
- User-facing SDLC documentation explains both modes and their default.
Prior art
Out of scope
- Approval after every implementation phase.
- A separate training or tutorial SDLC.
- Changing the autonomous default.
Problem
aidd-orchestrator:01-sdlccurrently exposes only an autonomous delivery contract. Teams also need a supervised path for decisions that should remain human-owned without manually interrupting the pipeline.Product decision
Reintroduce an optional interactive mode. Autonomous mode remains the default.
This deliberately revisits the single autonomous contract introduced by #517. It is not a regression to the former behavior: the new mode adds a small number of decision gates while keeping internal implementation and repair loops autonomous.
Modes
Interactive gates
aidd-dev:01-planproduces or revises the implementation plan. Reuse that skill’s approval point; do not add a duplicate gate.At each gate, present the artifact, material risks, the pending decision, and the next stage.
A rejection sends the feedback back to the artifact owner, then presents the revised gate again. Approved artifacts are resumed without regeneration. Telemetry must represent pauses and resumptions.
Acceptance criteria
Prior art
8f9e245.ed816044intentionally removed it in favor of one autonomous contract.Out of scope