github-copilot-agent-scrum-kit

Interface design for APIs (REST, GraphQL, gRPC, library/SDK, CLI) — consistency, evolvability, error design, versioning, backward compatibility. Use when: designing APIs, reviewing API contracts, versioning decisions, error response design, choosing between REST/GraphQL/gRPC. Triggers: API design, REST, GraphQL, gRPC, versioning, backward compatibility, error response, pagination, rate limiting, OpenAPI

Inject architectural thinking into technology selection, architecture decisions, and design judgments. Not a comparison table — a thinking framework that raises decision quality. Use when: technology stack selection, architecture pattern comparison, ADR creation, design review, non-trivial design decisions. Triggers: architecture selection, technology selection, design thinking, architecture decision, trade-off analysis

Data model selection, consistency trade-offs, data ownership, storage and processing decisions. Use when: choosing databases, designing data models, defining service data boundaries, replication/partitioning decisions, batch vs stream processing. Triggers: data model, database selection, consistency, replication, partitioning, CQRS, event sourcing, saga, aggregate design, transaction isolation

Code and module-level design judgment — complexity management, interface design, naming, abstraction depth, error handling philosophy, information hiding. Use when: writing new modules, reviewing code quality, refactoring decisions, API design, naming discussions. Triggers: design judgment, code quality, module design, complexity, naming, abstraction, error handling, code smell

Production reliability, deployment pipelines, release strategies, incident response, SLO design. Use when: designing for failure, planning releases, setting SLOs, incident response, postmortem review, deployment pipeline design. Triggers: resilience, reliability, SLO, circuit breaker, deployment strategy, canary, blue-green, incident, postmortem, DORA, rollback, bulkhead, timeout

When to refactor, what to refactor, how far to go. Technical debt classification, legacy code strategy, refactoring safety. Use when: deciding whether to refactor, scoping refactoring work, handling legacy code, classifying technical debt, choosing refactoring techniques. Triggers: refactoring, technical debt, code smell, legacy code, when to refactor, refactoring scope, debt payoff

Thinking like an attacker. Threat modeling, secure-by-default design, security trade-offs. Use when: designing authentication/authorization, reviewing code for vulnerabilities, making security vs usability trade-offs, threat modeling, handling secrets or user input. Triggers: security, threat model, STRIDE, OWASP, authentication, authorization, input validation, secrets, attack surface, vulnerability

Testing strategy and design decisions — what to test, how to test, when to mock, test classification, TDD rhythm. Use when: deciding test approach, choosing test scope, reviewing test quality, legacy code testing, mock vs real debate. Triggers: testing strategy, what to test, test design, mock, TDD, test pyramid, test doubles, legacy testing, characterization test