aiops

Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.

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.

Free-form thinking partner. Discuss ideas, compare options, name tradeoffs. No artifacts committed.

Break a plan or PRD into vertical-slice issues on the project issue tracker.

Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.

Keep source files under 500 lines. Split files that mix concerns — types, utils, hooks, sub-components, constants. Use when a file approaches the limit or when the user says refactor file, split file, too long, or file too big.

Diagnosis loop for hard bugs and performance regressions. Use when the user says diagnose/debug, or reports broken/failing/slow behavior.

Build and sharpen a project's domain model — glossary, ubiquitous language, ADRs. Use when changing the model, not just reading CONTEXT.md.

Compact the current conversation into a handoff document for another agent to pick up.

Git operations wrapper: sync, stage, commit, push. Generates Conventional Commits messages with .scratch artifact references. Use when the user says gitops, commit, push, sync code, or needs version control operations.

Generate HTML/CSS mockups for UI design. Produces browser-previewable mockup files with placeholder data. Use when the user says ui-mockup, mockup, design UI, wireframe, or needs visual reference for a feature.

Relentless interview that sharpens a plan and updates CONTEXT.md and ADRs as decisions land.

Interview the user relentlessly about a plan or design. Use when stress-testing a plan before building, or on any grill trigger phrase.

Minimal solution discipline: YAGNI ladder, stdlib and native first, shortest working diff. Use during delivery when writing code, or when the user says lean, lean mode, yagni, ponytail, lazy mode, or complains about over-engineering.

Throwaway prototype to answer a design question — terminal logic explorer or multi-variant UI on one route.

Review diffs for over-engineering only. One line per finding: location, what to cut, what replaces it. Hard gate before /review in aiops delivery. Use when the user says prune, simplify review, what can we delete, or over-engineered.

Test-driven development — vertical red-green-refactor slices through public interfaces.

Move issues and external PRs through triage roles — categorise, verify, grill if needed, write agent-ready briefs.