matiaspakua

test-master

Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

openspec-explore

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

openspec-sync-specs

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

openspec-update-change

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

openspec-triage

Turn an OpenSpec exploration report (a candidate feature/gap list) into real, estimated, prioritized GitHub Issues linked to a Use Case. Use after opsx:explore produces a report and before opsx:propose scaffolds any change from it.

agile-product-owner

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.

API & Backend Listed

api-contract-testing

Design, review or test API contracts and lifecycle quality. Use whenever a task mentions API-first, OpenAPI, REST, gRPC, schemas, endpoints, contract testing, mocks, compatibility, authentication, authorization, Postman/Newman, API documentation, performance or API versioning.

Web & Frontend Listed

architecture-decision-design

Create, review or evolve lightweight software architecture documentation and architecture decisions. Use whenever a task mentions SAD, ADRs, C4, UML, PlantUML, quality attributes, architecture tradeoffs, system context, components, deployment views, design alternatives or documenting why a technical choice was made.

DevOps & Infrastructure Listed

ci-cd-quality-gates

Design, review or improve CI/CD pipelines with fast feedback, reproducible builds, QA automation, security checks, artifact integrity, promotion and recovery. Use whenever a task mentions CI, CD, pipelines, builds, stages, quality gates, release promotion, registries, deployment, rollback, canary, blue/green, runners or pipeline failures.

delivery-maturity-roadmap

Assess DevSecOps, QA automation and software delivery maturity, then produce a context-sensitive adoption roadmap. Use whenever a user asks for a maturity assessment, DORA metrics, flow metrics, transformation plan, DevSecOps rollout, QA improvement roadmap, capability baseline, ROI or prioritization of engineering practices.

Code & Development Listed

devsecops-traceability

Build or audit end-to-end traceability for software delivery. Use whenever a task mentions requirements, user stories, issues, ADRs, architecture, tests, commits, pull/merge requests, releases, incidents, evidence, audit trails, or asks whether work is covered. Connect business intent through QA, security and operations, even when the user does not explicitly say traceability.

Web & Frontend Listed

hexagonal-architecture

Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services. Use when introducing or refactoring toward Ports and Adapters, or when domain logic has become entangled with I/O.

DevOps & Infrastructure Listed

operations-observability-readiness

Assess or design production readiness, observability and operational feedback for services and delivery pipelines. Use whenever a task mentions SRE, monitoring, logs, metrics, traces, health checks, SLOs, alerts, runbooks, capacity, reliability, rollback, incidents or operating a service after deployment.

qa-automation-strategy

Design or review a risk-based QA and test automation strategy across the software lifecycle. Use whenever a user asks for a test plan, test pyramid, acceptance criteria, regression strategy, unit/integration/E2E/API/security/performance testing, fixtures, test data, automation scope, evidence or coverage. Trigger even if the request only mentions automating tests for one feature.

java

This skill should be used when the user asks to "write java code", "java best practices", "jdk features", "java records", "java streams", "java optional", "java testing", "java spring", "java patterns", or needs guidance on professional Java development.

software-functional-analyst

Expert software functional analyst specializing in functional requirements analysis, use case modeling, data flow design, and database analysis. Use when analyzing business requirements, creating use cases, designing data flows, modeling databases, or translating business needs into technical specifications.

API & Backend Listed

senior-backend

This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs". Use for Node.js/Express/Fastify development, PostgreSQL optimization, API security, and backend architecture patterns.

DevOps & Infrastructure Listed

senior-devops

Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.

Data & Documents Listed

drawio

Always use when user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF.

design-doc-mermaid

Create Mermaid diagrams (activity, deployment, sequence, architecture) from text descriptions or source code. Use when asked to "create a diagram", "generate mermaid", "document architecture", "code to diagram", "create design doc", or "convert code to diagram". Supports hierarchical on-demand guide loading, Unicode semantic symbols, and Python utilities for diagram extraction and image conversion.

Data & Documents Listed

plantuml

Generate PlantUML diagrams — class, sequence, use case, activity, state, component, deployment, object, entity-relationship/data-model, C4 model (context/container/component/dynamic/deployment), timing, mindmap, WBS, Gantt, network, ArchiMate, JSON/YAML, and wireframe (salt) diagrams — for software architecture, system design, and documenting complex codebases. Use whenever asked to create, draw, sketch, generate, or update a UML diagram, architecture diagram, sequence diagram, class diagram, ER/data-model diagram, deployment diagram, component diagram, C4 diagram, state machine, or any software-engineering diagram, or when PlantUML, .puml files, or "UML diagram" comes up — even without saying "PlantUML" by name, just describing wanting a diagram of code, architecture, API flow, or a database schema. Also use to render an existing .puml file to SVG/PNG/PDF, or to debug broken PlantUML syntax.