STANDARD OPERATING PROCEDURE
Purpose
Run full-stack AI-assisted development loops—framing, architecture, implementation, validation, and launch—while keeping confidence ceilings explicit and artifacts auditable.
Trigger Conditions
- Positive: end-to-end feature delivery, AI-assisted coding reviews, test orchestration, release-readiness drills, backlog triage for complex builds.
- Negative: single-file edits without coordination, pure prompt engineering (route to prompt-architect), or meta-skill creation (route to skill-forge).
Guardrails
- Skill-Forge structure-first: ensure
SKILL.md, examples/, and tests/ exist; stage resources/ and references/ or log remediation tasks before completion.
- Prompt-Architect clarity: capture HARD/SOFT/INFERRED requirements, user acceptance criteria, and produce pure-English outputs with ceiling-aware confidence.
- SDLC safety: enforce branch/CI policy, code review checkpoints, test coverage gates, and rollback/feature-flag plans for risky changes.
- Adversarial validation: probe failure modes (flaky tests, dependency drift, latency regressions) and record evidence.
- MCP tagging: store orchestration logs under WHO=
ai-dev-orchestration-{session} and WHY=skill-execution for reuse.
Execution Playbook
- Intent & scope: map goals to release milestones; confirm non-functional targets (latency, reliability, compliance).
- Plan & topology: assign planner, builder, reviewer, and tester agents; define lanes, SLAs, and review cadence.
- Build & delegate: break work into increments, wire hooks to CI, and enforce registry-only agent usage.
- Quality gates: run unit/integration/e2e suites, security/lint checks, and performance baselines with thresholds.
- Adversarial loop: simulate rollback, partial failures, and migration paths; document deltas and evidence.
- Delivery: summarize implemented changes, validation results, residual risk, and next actions with confidence ceiling.
Output Format
- Release objective, scope, and constraints.
- Role topology (planner/builder/reviewer/tester) with ownership and timelines.
- Delivery plan and checkpoints (CI hooks, review gates).
- Validation evidence (tests, performance, security) and risk log.
- Confidence:
X.XX (ceiling: TYPE Y.YY) - rationale in pure English.
Validation Checklist
- Structure-first assets present or ticketed; examples/tests updated or planned.
- HARD/SOFT/INFERRED requirements addressed with owners and evidence.
- CI/review gates executed; rollback path documented; hooks within latency budgets.
- Adversarial and COV runs logged with MCP tags; confidence ceiling declared.
Completion Definition
Feature is deliverable when code, tests, and deployment assets meet acceptance criteria, risks are owned, rollback is ready, and orchestration notes persist in MCP.
Confidence: 0.70 (ceiling: inference 0.70) - SOP reframed with skill-forge structure, prompt-architect constraint handling, and SDLC orchestration guardrails.
1---2name: ai-dev-orchestration3description: Coordinate multi-agent software delivery with guardrails for planning, implementation, testing, and release.4---5
6
7
8
9## STANDARD OPERATING PROCEDURE
10
11### Purpose
12Run full-stack AI-assisted development loops—framing, architecture, implementation, validation, and launch—while keeping confidence ceilings explicit and artifacts auditable.
13
14### Trigger Conditions
15- **Positive:** end-to-end feature delivery, AI-assisted coding reviews, test orchestration, release-readiness drills, backlog triage for complex builds.
16- **Negative:** single-file edits without coordination, pure prompt engineering (route to prompt-architect), or meta-skill creation (route to skill-forge).
17
18### Guardrails
19- **Skill-Forge structure-first:** ensure `SKILL.md`, `examples/`, and `tests/` exist; stage `resources/` and `references/` or log remediation tasks before completion.
20- **Prompt-Architect clarity:** capture HARD/SOFT/INFERRED requirements, user acceptance criteria, and produce pure-English outputs with ceiling-aware confidence.
21- **SDLC safety:** enforce branch/CI policy, code review checkpoints, test coverage gates, and rollback/feature-flag plans for risky changes.
22- **Adversarial validation:** probe failure modes (flaky tests, dependency drift, latency regressions) and record evidence.
23- **MCP tagging:** store orchestration logs under WHO=`ai-dev-orchestration-{session}` and WHY=`skill-execution` for reuse.
24
25### Execution Playbook
261. **Intent & scope:** map goals to release milestones; confirm non-functional targets (latency, reliability, compliance).
272. **Plan & topology:** assign planner, builder, reviewer, and tester agents; define lanes, SLAs, and review cadence.
283. **Build & delegate:** break work into increments, wire hooks to CI, and enforce registry-only agent usage.
294. **Quality gates:** run unit/integration/e2e suites, security/lint checks, and performance baselines with thresholds.
305. **Adversarial loop:** simulate rollback, partial failures, and migration paths; document deltas and evidence.
316. **Delivery:** summarize implemented changes, validation results, residual risk, and next actions with confidence ceiling.
32
33### Output Format
34- Release objective, scope, and constraints.
35- Role topology (planner/builder/reviewer/tester) with ownership and timelines.
36- Delivery plan and checkpoints (CI hooks, review gates).
37- Validation evidence (tests, performance, security) and risk log.
38- **Confidence:** `X.XX (ceiling: TYPE Y.YY) - rationale` in pure English.
39
40### Validation Checklist
41- Structure-first assets present or ticketed; examples/tests updated or planned.
42- HARD/SOFT/INFERRED requirements addressed with owners and evidence.
43- CI/review gates executed; rollback path documented; hooks within latency budgets.
44- Adversarial and COV runs logged with MCP tags; confidence ceiling declared.
45
46### Completion Definition
47Feature is deliverable when code, tests, and deployment assets meet acceptance criteria, risks are owned, rollback is ready, and orchestration notes persist in MCP.
48
49Confidence: 0.70 (ceiling: inference 0.70) - SOP reframed with skill-forge structure, prompt-architect constraint handling, and SDLC orchestration guardrails.
majiayu000