01 Sdlc

Skill: sdlc

Behavior

Operate autonomously from the request to a draft pull request: decide and act without confirmation, asking only before spending money, taking an irreversible action, or making a decision that requires user authority. Read only the current zone reference. Verify that every named provider is installed before calling it.

Spawn specialized agents for isolated work. Parallelize independent work when it is faster. Give each agent one focused task that a smaller model can execute. Repeat the responsible zone when delegated work returns an actionable gap.

---
title: SDLC orchestration
---
flowchart TD
  subgraph FrameStage["01 Frame"]
    direction TB
    Request["$request"]
    Frame["01 Frame"]
  end

  subgraph DeliverStage["02 Deliver"]
    direction TB
    Deliver["02 Deliver"]
  end

  subgraph CheckStage["03 Check"]
    direction TB
    Check["03 Check"]
    PullRequest["$pull_request"]
  end

  Request --> Frame
  Frame --> Deliver
  Deliver --> Check
  Check --> PullRequest

  classDef artifact fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:2px
  classDef zone fill:#F1F5F9,stroke:#64748B,color:#0F172A,stroke-width:2px

  class Request,PullRequest artifact
  class Frame,Deliver,Check zone

Say when this orchestration is over

Once the draft pull request exists, and only then, run:

echo "aidd:step-end aidd-orchestrator:01-sdlc"

No host reports when an orchestration finished. A skill call's own result comes back in a tenth of a second, which is the dispatch and not the completion, so a measurement that never hears this ends the run at the next pause — and an orchestration is mostly pauses. Everything it drove afterwards then reads as work that belonged to nothing.

References