Menu
Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.
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
Flow Conductor for the aiops bundle. One entry — infers task type, shows plain-language steps, tracks journey in flow.state.yaml, dispatches skill + agent per phase.
Structured design process for the architect agent. Guides from grill conclusions to complete NOTES.md + tech-spec.md plus needed domain documentation updates through constraint gathering, module identification, interface design, alternative exploration, and risk analysis. Use when the architect needs to produce design decisions and technical specifications.
Build and query a persistent code graph for the target project. Uses graphify (Tree-sitter + Louvain clustering) for deterministic structural extraction, then the model adds semantic annotations. Use when the user says build graph, code graph, dependency graph, impact analysis, or when other skills need structured code understanding before proceeding.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user says architecture review, codebase health, deepening, refactor suggestions, or complains about architectural friction.
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.
Configure a target project for the aiops bundle — issue tracker, triage labels, domain doc layout. Silent defaults on inline bootstrap; full prompts on explicit /aiops-setup.
| name | aiops-implement |
| description | Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval. |
| disable-model-invocation | true |
Implement from PRD, issue brief, or tech-spec. Not for grill/alignment — lean active only while writing code.
Invoked by Flow Conductor delivery phase (builder agent). Update flow.state.yaml → delivery_sub_phase as you progress.
issues/<current> AC, or tech-spec.md + NOTES.mdDESIGN_REVIEW.md APPROVE when design review ran in this flow/prototype ran: VERDICT.md before absorbing prototype learningsIf graphify-out/graph.json exists, tell the user "查询代码图谱评估修改影响面" then query /code-graph query impact <target-file> before writing code to understand the blast radius. Log affected modules in the journey context so the builder knows what might break.
Run sub-phases in order. Do not skip unless user explicitly exempts a step (e.g. mechanical fix → skip new tests).
| Sub-phase | delivery_sub_phase | Who | Skill / action | Gate to advance |
|---|---|---|---|---|
| 1 | implement | builder | lean ladder + write code | Tests for changed behaviour pass |
| 2 | implement | builder | /tdd at public interfaces | Red-green on agreed surface |
| 3 | prune | quality-auditor | /prune on diff | Findings listed or "Lean already" |
| 4 | review | code-reviewer | /review vs NOTES/tech-spec/issue | REVIEW.md APPROVE |
| 5 | ready_for_commit | — | Set journey gate ready_for_commit | User may ask gitops to ship |
Record in journey gates_satisfied: prune_done, review_approve, ready_for_commit.
If any file you touch approaches 500 lines, invoke /file-refactor before advancing to prune — split per that skill (types → utils → hooks → sub-components). Skip only when the user exempts or the file is intentionally monolithic.
When .scratch/<slug>/tasks.md contains YAML frontmatter with waves:, execute tasks wave by wave:
waves list from frontmatter.If no tasks.md frontmatter exists, implement tasks sequentially in document order.
Commit — only when user explicitly asks. Never commit autonomously. Shipping is /gitops in conductor ship phase.
Run typechecking and targeted tests during implement; full suite once before review.
Sub-phase 1–2: 「写代码 + 测试」→ sub-phase 3: 「精简 diff」→ sub-phase 4: 「对照设计评审」→ sub-phase 5: 「等你确认再提交」.
Alignment uses /grill-with-docs without lean. Switch to lean when sub-phase implement starts.