Menu
Guide committed work to readiness and execute CI Sync, CI Async, or the full governed ProdOps delivery flow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Proactive drift-scan cycle. Reads all active OBCs and Issues, identifies divergences, and repairs what can be automated. Runs across the entire active backlog, not for a specific OBC.
Read all active OBCs and compare declared state with backlogs and external tools. Produces a divergence list. Does not repair — only identifies gaps.
Event-driven cycle triggered by a product decision. Captures the decision as an OBC, attaches a Work Item, promotes it through the backlog hierarchy, and closes it when the OBC reaches Operational. Runs for a specific OBC.
Create or update an OBC from the decision that triggered the Diligence Sync cycle. Use when an Assessment decision, Discovery experiment, or Operation signal requires canonical state to be recorded before Work Items are created.
Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.
Classify divergences from Scan and register them as pending Diligence items with severity and corrective action. Does not repair — only signals.
| name | downstream |
| description | Guide committed work to readiness and execute CI Sync, CI Async, or the full governed ProdOps delivery flow. |
Downstream is the complete, governed execution mode. Commitment may be declared before every prerequisite exists; the orchestrator must guide the item toward readiness and stop at each missing gate. It must never bypass or invent a prerequisite.
| Command | Scope |
|---|---|
/downstream ci-sync <capability> | Readiness → Bootstrap → Hack → Sync → Finish |
/downstream ci-async <capability> | Readiness and CI Sync evidence check → Ship → Validate → Promote |
/downstream full <capability> | Readiness → CI Sync → CI Async |
Until CI Async automation is complete, /downstream without a scope defaults to ci-sync and must report that choice explicitly.
Before executing either cycle, evaluate the capability against all current Downstream prerequisites:
prodops/artifacts/obcs/.prodops/artifacts/bdd/.prodops/artifacts/risks/risks.md.Entrou.Treat commitment as Downstream Declared. If any applicable prerequisite is missing, stop before execution, identify the owning journey or artifact, and state the next action. Mark Downstream Ready only after every applicable gate passes; Delivery Started begins only when Bootstrap starts for that Ready item.
When all prerequisites exist, generate prodops/exec/cards/<card-slug>/context.md from prodops/templates/delivery/context-capsule.md. The capsule is generated by Downstream readiness, not Bootstrap.
start, tdd, and commit; start owns Git flow and branch creation.prodops/framework/execution-mapping/work-item-schema.md.[Artifact ID]: description. Set operation:<value> and artifact-type:<value> as labels.