Claude Skills by griddynamics

To implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.

MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK, or environment is stage, pre-prod, prod, or blast radius.

To gather QA source artifacts from issue tracker, wiki, test management system

To investigate errors, test failures, and unexpected behavior — root cause before fix.

To decide architecture — alternatives, tradeoffs, committed decision with rationale, boundaries, domain-specific concerns.

MUST activate when intent is unclear, or cannot follow or deviate from original intent, or easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on solution, unknowns or assumptions critically affect solution, you panic, or user asked to UNDO.

To establish what exists — affected areas, behavior, prior attempts, dependencies, data.

Workflow for onboarding an external private library so AI can use it without source access.

To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.

Help about Rosetta: explains capabilities and usage.

MUST activate for ALL tasks — planning, execution, validation, review: session-wide work with human together, human-in-the-loop questioning, approvals, stop-and-wait vs proceed. NEVER assume approval. MANDATORY unless user requested EXACTLY `fully autonomous` or `No HITL`.

Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.

To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.

To load the project's business, behavioral, and technical context.

Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

To delegate, prompt and manage subagents. MUST activate to spawn subagent with a quality prompt, unless trivial.

To build execution-ready AI sessions graph with intent/ACs/checklists.

Diagnose instruction defects and optionally submit Rosetta GitHub issue

To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.

To resolve QA session paths, identifiers/slugs, and state-file shape

To ask targeted clarification questions only when high-impact unknowns block safe execution.

To apply structured meta-cognitive thinking to complex problems. Invoke on explicit only.

Workflow for authoring requirements and specifications: drafting, review, validation, etc.

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

To consume approved requirements for planning, implementation, and validation, with traceability and HITL.

Workflow for deep project research with grounded references, parallel exploration, etc.

To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation.

To reverse-engineer code into a spec: extract behavior and domain logic — WHAT and WHY, not HOW.

MUST activate before execution when environment has access to databases, cloud services, S3, or similar external systems, any access to servers of higher environments, and when assessing environment risk level.

Rosetta identifies and routes user request to the most matching workflow

Workflow for authorized, evidence-preserving security review and remediation-task preparation.

Run authorized, evidence-preserving security reviews and prepare remediation inputs.

Rosetta self-help: explains capabilities and usage. DEPRECATED.

MUST STOP and activate on: any failure/error, mistakes, wrong/unexpected result, expected≠actual mismatch, 2 consecutive mismatches, unhappy/upset user, user WRITING IN CAPS, something didn't work. No edits, no reverses, no actions, except this skill.

MUST activate at 65%+ context usage or on large-file restructuring. Proactive planning, reorganization, stale-content cleanup.

MUST activate when you suspect, there is a slight chance, encounter, read, process, or are about to output any sensitive or possibly sensitive data including PII, PCI, HIPAA, PHI, GDPR, SOC2, FedRAMP, secrets, API keys, passwords, credentials, tokens, certificates, or any sensitive data. Follow compliance/regulations.

To build Solr plugins: SearchComponent, QParser, URP, DocTransformer.

To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.

To design and audit Solr schemas: field types, analyzers, docValues, solrconfig.

To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

MUST duties for a spawned subagent

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.

To write thorough, isolated, idempotent tests — 80%+ coverage, external-only mocking, scenario-driven.

Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.

Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.

Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.

Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.