C4 model diagrams, component relationships, and architectural pattern identification. Trigger: "map architecture", "C4 diagram", "component diagram", "system context".

Architecture proposals with trade-off analysis, alternatives matrix, and decision rationale. Trigger: design architecture, propose solution, evaluate alternatives, create ADR.

Developer experience friction analysis, onboarding quality, and tooling assessment. Trigger: "audit DX", "developer experience", "onboarding quality", "developer friction".

REST, GraphQL, and gRPC contract analysis including versioning, consistency, and completeness. Trigger: "analyze API", "API surface", "endpoint audit", "contract analysis".

CI/CD security hardening, SLSA supply chain levels, secrets management, SAST/DAST integration, and shift-left security practices. Trigger: "devsecops", "CI/CD security", "SLSA", "supply chain", "SAST", "DAST", "shift-left security".

Contract-first API design producing OpenAPI specs, GraphQL schemas, or protobuf definitions with versioning strategy. Trigger: "design API", "OpenAPI spec", "GraphQL schema", "protobuf definition", "API contract".

REST, GraphQL, and gRPC API governance, versioning strategy, rate limiting, and developer experience design. Trigger: "API architecture", "API design", "REST", "GraphQL", "gRPC", "API governance", "developer experience".

dbt-style transformations, dimensional data modeling, testing strategies, and documentation generation for analytics platforms. Trigger: "analytics engineering", "dbt", "data modeling", "dimensional model", "star schema", "data marts".

Produces Architecture Decision Records following the Nygard/MADR template with full context, consequences, and traceability. Trigger: "generate ADR", "document decision", "architecture decision record", "record this decision".

Root cause analysis, risk detection, technical debt quantification, and friction identification. Trigger: diagnose issue, find root cause, assess risk, quantify debt, detect friction.

Implement WCAG 2.1 AA / 2.2 accessibility: semantic HTML audit, ARIA implementation, keyboard navigation, screen reader testing, color contrast. Use when user asks to "implement accessibility", "fix a11y issues", "make WCAG compliant", or "audit for accessibility".

Designs RPO/RTO targets, failover procedures, backup strategies, and tabletop exercises for disaster recovery. Trigger: "disaster recovery", "DR plan", "RPO RTO", "failover", "backup strategy", "business continuity".

Writes testable acceptance criteria in Given/When/Then format, covering happy paths, edge cases, and error scenarios. Trigger: "acceptance criteria", "given when then", "write AC", "define done", "user story criteria".

Report a bug against an existing feature — creates a structured bugs.md record, generates fix tasks in tasks.md, and optionally imports from or creates GitHub issues. Use when fixing a bug, reporting a defect, importing a GitHub issue into the workflow, or triaging an error without running the full specification process.

Produces structured handover packages that bridge analysis to implementation, ensuring zero knowledge loss. Trigger: "handover", "transition to implementation", "delivery package".

Orchestrates full technical analysis pipelines, coordinating multiple skills and agents into coherent discovery workflows. Trigger: "run discovery", "full analysis", "orchestrate pipeline".

Documentation freshness, coverage, accuracy, and maintainability assessment. Trigger: "audit docs", "documentation review", "doc coverage", "README check".

Generates README files, API documentation, operational runbooks, and Architecture Decision Records (ADRs). Trigger: "generate docs", "write README", "create runbook", "write ADR", "API documentation".

Validate cross-artifact consistency — checks that every spec requirement traces to tasks, plan tech stack matches task file paths, and constitution principles are satisfied across all artifacts. Use when running a consistency check, verifying requirements traceability, detecting conflicts between design docs, or auditing alignment before implementation begins.

Generate Gherkin .feature files from requirements before implementation — produces executable BDD scenarios with traceability tags, computes assertion integrity hashes, and locks acceptance criteria for test-driven development. Use when writing tests first, doing TDD, creating test cases from a spec, locking acceptance criteria, or setting up red-green-refactor with hash-verified assertions.