workshop-datacorp-team-kit

"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."

"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."

"Use when drafting Architecture Decision Records, evaluating alternatives, or documenting technical trade-offs. Triggers on "ADR", "architecture decision", "trade-off", "pick between", "why did we choose"."

"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."

Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.

Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.

Use when investigating slow queries, designing indexes, or reviewing execution plans. Triggers on 'slow query', 'explain plan', 'index', 'query tuning', 'N+1', 'table scan'.

Use when planning an online schema change, zero-downtime migration, or rolling back a deploy that changed a table. Triggers on 'migration', 'ALTER TABLE', 'zero-downtime', 'expand-contract', 'backfill'.

Use when a test is intermittent, when asked to investigate CI instability, 'quarantine a flaky test', or to build a flaky-test dashboard.

Use when asked to design a test strategy, choose a test pyramid shape, define coverage targets, or evaluate testing investments across unit / integration / E2E layers.

Use when reviewing Terraform, Bicep, or CloudFormation, checking for drift, or hardening infrastructure code. Triggers on 'review terraform', 'review bicep', 'IaC review', 'drift detection', 'state file'.

Use when hardening a CI/CD pipeline, moving to OIDC, signing artifacts, or meeting SLSA requirements. Triggers on 'SLSA', 'supply chain', 'OIDC', 'sigstore', 'cosign', 'pipeline security', 'GHA hardening'.

"Use when reviewing documentation for style, clarity, inclusive language, or Microsoft/Google style guide compliance. Triggers on "doc review", "style guide", "plain language", "inclusive language", "readability"."

"Use when refining backlog items, splitting epics, or validating INVEST criteria. Triggers on "refine story", "split epic", "acceptance criteria", "user story", "INVEST"."

"Use when drafting or reviewing OKRs, aligning team work to business outcomes, or translating goals into measurable results. Triggers on "OKR", "key result", "business goal", "outcome", "quarterly planning"."

"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."

"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."

"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."

"Use when forecasting team capacity, planning quarterly work, or deciding what to cut. Triggers on "capacity", "forecast", "roadmap", "can we ship it", "headcount", "planning"."

"Use when reviewing a UI for usability defects, running a Nielsen heuristic evaluation, or auditing accessibility. Triggers on "UX review", "heuristic", "usability", "Nielsen", "WCAG", "a11y", "accessibility audit"."

"Use when designing or running a sprint retrospective, when the same retros keep producing no change, or when team morale needs attention. Triggers on "retro", "retrospective", "sprint review", "team health", "sailboat", "start stop continue"."

"Use when starting a project, running a risk review, or updating mitigations. Triggers on "risk", "risk register", "mitigation", "contingency", "what could go wrong"."

"Use when reviewing or designing an Azure landing zone, enforcing platform guardrails, or auditing a new subscription. Triggers on "landing zone", "management group", "platform baseline", "guardrails", "CAF", "subscription vending"."

Use when a test is intermittent, when asked to investigate CI instability, 'quarantine a flaky test', or to build a flaky-test dashboard.

"Use when designing a User Acceptance Test plan, defining exit criteria, or coordinating business sign-off. Triggers on "UAT", "user acceptance", "business validation", "sign-off", "go/no-go"."

Use when defining data quality rules, schema contracts, or SLA monitoring for a dataset. Triggers on 'data quality', 'great expectations', 'schema contract', 'data SLA', 'data validation', 'null check'.

Use when designing a new data pipeline, choosing between batch and streaming, or laying out a medallion / lakehouse architecture. Triggers on 'data pipeline', 'ETL', 'ELT', 'medallion', 'bronze silver gold', 'streaming vs batch'.

Use when evaluating an ML model, choosing metrics, designing offline/online tests, or checking fairness. Triggers on 'evaluate model', 'model metrics', 'A/B test model', 'fairness', 'holdout', 'confusion matrix'.

Use when building a retrieval-augmented generation system, choosing a chunking strategy, or evaluating retrieval quality. Triggers on 'RAG', 'retrieval-augmented', 'vector search', 'chunking', 'embeddings', 'hallucination'.

"Use when preparing release notes, classifying changes, or drafting upgrade/breaking-change communications. Triggers on "release notes", "changelog", "version", "ship", "customer-facing communication"."

Use when designing a new system, onboarding a feature to security review, or running STRIDE. Triggers on 'threat model', 'STRIDE', 'attack tree', 'trust boundary', 'data flow diagram', 'DFD'.

Use when triaging CVEs, prioritizing vulnerabilities, or setting remediation SLAs. Triggers on 'CVE', 'vulnerability triage', 'CVSS', 'EPSS', 'SLA for patching', 'reachability'.

"Use when collecting evidence for a compliance audit (SOC 2, ISO 27001, PCI-DSS, LGPD), responding to an auditor request, or building a continuous-compliance stream. Triggers on "audit", "evidence", "SOC 2", "ISO 27001", "PCI", "LGPD", "control", "compliance"."

Use when responding to a production incident, running a post-incident review, or designing an on-call runbook. Triggers on 'incident', 'outage', 'postmortem', 'runbook', 'page', 'sev1', 'sev2'.

Use when defining Service Level Objectives, error budgets, or SLIs for a service. Triggers on 'SLO', 'SLI', 'error budget', 'availability target', 'latency target'.

Use when investigating slow queries, designing indexes, or reviewing execution plans. Triggers on 'slow query', 'explain plan', 'index', 'query tuning', 'N+1', 'table scan'.

Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.

"Use when preparing a conference talk, customer demo, or workshop, and you need a reliable, reproducible script. Triggers on "demo", "talk", "workshop", "keynote", "prepare presentation", "live coding"."

Use when embedding security into the SDLC, mapping to NIST SSDF, or defining security gates. Triggers on 'secure SDLC', 'SSDF', 'security gates', 'shift left', 'paved road', 'security checkpoints'.