devco-agent-skills

Grill ambiguity, surface assumptions, extract vocabulary. Run before Plan when requirements vague (standard lane) or always (high-stakes lane). Output feeds Plan + Spec gates.

Tournament-style solution exploration. Generates 2-5 options with adversarial challenges, recommends with trade-offs. Mandatory high-stakes (≥3 options), conditional standard (multi-path).

Incrementally fix Java/Gradle/Maven build and compilation errors for Spring Boot projects. One error at a time for safety.

Execute gate — dispatches one slice-executor subagent per plan slice (parallel where independent). Reads plan + spec + pre-flight 4 artifact. Lane-aware (trivial: direct execute, no dispatch).

Create and validate Flyway database migrations for schema changes. Supports MySQL and PostgreSQL.

> Common protocol ALL agents follow. Referenced via `protocol: _shared-protocol.md` frontmatter.

High-stakes lane pre-plan architectural review. Reads ADRs + CONTEXT.md + brainstorm artifact. Validates chosen solution against existing architecture. Output feeds Plan gate. Optional for standard lane, auto-fire for high-stakes.

Build and compilation error resolution specialist for Java/Gradle/Maven projects. Use PROACTIVELY when build fails or compilation errors occur. Fixes build/compilation errors only with minimal diffs, no architectural edits. When NOT to use: for test failures (use slice-executor), for architectural refactoring (use planner).

Stage 2 of two-stage review. Spec compliance already verified by Stage 1. Reviews security, performance, maintainability, readability, test quality. Severity-tagged output (P0/P1/P2/P3/P4) with MANDATORY rule ID citation per finding.

Decompose chosen solution into vertical slices with dependency graph + risk register. Consumes Align + Brainstorm artifacts. Output feeds Spec gate. Use after Brainstorm gate (high-stakes) or directly after Align (standard with obvious solution).

Surface ambiguity, missing requirements, hidden assumptions BEFORE planning. Fires after triage for standard (vague request) or high-stakes (always). Updates CONTEXT.md vocabulary. Produces agreed-requirements artifact feeding Plan gate.

REST API design patterns for Spring Boot — HTTP methods, status codes, URL conventions, RFC 7807 ProblemDetail errors, pagination, versioning, validation, and OpenAPI documentation. Use when designing REST endpoints, choosing HTTP status codes, implementing error responses, adding pagination to list APIs, versioning APIs, or generating OpenAPI/Swagger specs.

Hexagonal architecture, DDD, CQRS, and event sourcing for Java Spring applications. Use when designing package structure, creating Aggregate Roots or Value Objects, implementing ports and adapters, setting up CQRS command/query separation, wiring domain events, writing ArchUnit tests, or creating solution architecture documents and ADRs.

Foundation skill — auto-loads at SessionStart. Teaches 5-layer adaptive workflow, 1% pre-flight discovery rule, triage routing, skill announcement contract, project detection. All other skills depend on this. Do NOT manually load.

Tournament-style iterative solution exploration. Generates 2-5 candidates via adversarial challenges, compares multi-dimensionally, recommends with explicit trade-offs. Mandatory high-stakes (≥3), conditional standard. Output feeds Plan + ADR for high-stakes.

19 hooks across 7 events