griddynamics
- 134 skills
- 0 followers
- 1 day ago last updated
- ▌ Hitl 2 · griddynamicsRosetta CRITICAL MUST skill to load as Prep Step 3 Step 2 — immediately after orchestrator-contract, right before loading any workflow. Loads the session-wide approval-gate protocol governing when to stop and wait vs proceed. WITHOUT IT decisions proceed silently, violating enterprise policy. Activate it for ALL tasks always — planning, execution, validation, review — regardless of auto-mode, no approval policy, full access. THE ONLY exception: user DIRECTLY EXPLICITLY requests with EXACTLY `fully autonomous` or `No HITL`. Without explicit opt-out this skill is MANDATORY. Do not assume approval from a question or partial response. Contains human-in-the-loop collaboration, questioning, approvals, and user coordination requirements. Auto mode, full access, etc ONLY means automatic approval of tool permission prompts, HITL stays!
- ▌ Coding 2 · griddynamics bundleTo implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.
- ▌ Testing 2 · griddynamicsTo write thorough, isolated, idempotent tests — 80%+ coverage, external-only mocking, scenario-driven.
- ▌ Planning 2 · griddynamics bundleTo build execution-ready plans from approved intent/specs with EARS, sequenced WBS, and HITL checkpoints.
- ▌ Research 2 · griddynamicsTo run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation.
- ▌ Debugging 2 · griddynamicsTo investigate errors, test failures, and unexpected behavior — root cause before fix.
- ▌ Deviation 2 · griddynamicsRosetta CRITICAL MUST skill. MUST activate when intent is unclear, you cannot follow original intent, you cannot easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on your solution, you detect unknowns or assumptions that critically affect the solution, you detect deviation NOT complying with original intent, you panic, or user asked to UNDO.
- ▌ Reasoning 2 · griddynamicsTo apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.
- ▌ Tech Specs 2 · griddynamicsTo define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
- ▌ Post Mortem 2 · griddynamics bundleDiagnose instruction defects and optionally submit Rosetta GitHub issue
- ▌ Post Mortem 3 · griddynamicsDiagnose instruction defects and optionally submit Rosetta GitHub issue
- ▌ Questioning 2 · griddynamicsTo ask targeted clarification questions only when high-impact unknowns block safe execution.
- ▌ Specflow Use 2 · griddynamics bundleTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
- ▌ Specflow Use 3 · griddynamics bundleTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
- ▌ Security 2 · griddynamics bundleRun authorized, evidence-preserving security reviews and prepare remediation inputs.
- ▌ Self Learning 2 · griddynamicsMUST activate on: execution failure/error, mistake, wrong/unexpected result, expected≠actual mismatch, 2 consecutive mismatches, unhappy/upset user, user asks why something failed/didn't work.
- ▌ Sensitive Data 2 · griddynamicsRosetta CRITICAL MUST skill. 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 data that could potentially be sensitive. Applicable for coding too
- ▌ Natural Writing 2 · griddynamicsTo rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.
- ▌ Risk Assessment 2 · griddynamicsMUST activate before execution when environment has access to databases, cloud services, S3, or similar external systems, and when assessing environment risk level. SHOULD be invoked manually before any new environment interaction.
- ▌
- ▌ Specflow Use 4 · griddynamics bundleTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
- ▌ Adhoc Flow 2 · griddynamicsWorkflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
- ▌ Dangerous Actions 2 · griddynamicsRosetta CRITICAL MUST skill. MUST activate when action or its consequence is potentially dangerous, potentially irreversible, potentially destructive, or HIGH RISK. MUST activate when consequence MAYBE dangerous even if action itself seems safe. This is enterprise environment — the cost of dangerous activities is EXTREMELY HIGH, recovery may be impossible, and blast radius may affect production, shared environments, or other teams. If there is even a remote chance - load the skill.
- ▌ Self Organization 2 · griddynamicsFor proactive planning, large-file restructuring (~500+ lines or 10K+ size), and stale-information cleanup. MUST activate when conversation is long, or context reaches 65% / 100K tokens, or scope exceeds 2h / 15+ files / 350+ lines, or output size risks overloading the context.
- ▌ Coding Flow 2 · griddynamicsWorkflow for all coding: features, fixes, refactors, unit tests, etc.; scales small to large.
- ▌ UI Aqa Flow 2 · griddynamics bundleWorkflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
- ▌ Coding Agents Farm 2 · griddynamicsTo orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
- ▌ API Aqa Flow 2 · griddynamics bundleWorkflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
- ▌ Testgen Flow 2 · griddynamics bundleWorkflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
- ▌ Reverse Engineering 2 · griddynamicsTo reverse-engineer code into a spec: extract behavior and domain logic — WHAT and WHY, not HOW.
- ▌ Research Flow 2 · griddynamicsWorkflow for deep project research with grounded references, parallel exploration, etc.
- ▌ Security Flow 2 · griddynamics bundleWorkflow for authorized, evidence-preserving security review and remediation-task preparation.
- ▌ Coding Flow 3 · griddynamicsLight coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
- ▌
- ▌ Coding Flow 4 · griddynamicsLight coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
- ▌ Large Workspace Handling 2 · griddynamicsTo partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
- ▌ Code Analysis Flow 2 · griddynamicsWorkflow for reverse-engineering a codebase into grounded architecture docs, requirements capture, etc.
- ▌ Init Workspace Flow 2 · griddynamics bundleWorkflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
- ▌ Coding Agents Hooks Authoring 2 · griddynamicsTo author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
- ▌ Coding Agents Prompt Authoring 2 · griddynamics bundleTo author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
- ▌ Post Mortem 4 · griddynamics bundleDiagnose instruction defects and optionally submit Rosetta GitHub issue
- ▌ Specflow Use 5 · griddynamics bundleTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
- ▌ Requirements Authoring Flow 2 · griddynamicsWorkflow for authoring requirements and specifications: drafting, review, validation, etc.
- ▌ Coding Agents Prompting Flow 2 · griddynamicsWorkflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.
- ▌ Pr Desc · griddynamicsUpdate the current PR description based on commits vs main. Writes a concise summary, entrypoint, and details section.
- ▌ Gain Backport · griddynamicsClassify a fix made to a GAIN-generated workspace app and propagate it to the right level — GAIN harness prompt, spec template, or documentation. Prevents the same issue from recurring in future runs.
- ▌
- ▌ Creating Commits · griddynamicsCreate well-structured git commits with clear, conventional commit messages. Use this skill whenever the user asks to commit changes, "commit this", "save my work", "make a commit", "write a commit message", or after completing a coding task when changes need to be committed. Also use when the user asks to split changes into multiple commits, amend a commit, or improve an existing commit message.
- ▌
- ▌ Deploy Requirements · griddynamicsGenerate a customer-specific deployment requirements document from the template. Takes customer name and known infrastructure details as input. Produces a filled-in requirements spec ready for human review before sending to the customer.
- ▌ Backend Quality Gate · griddynamicsAfter substantive edits under backend/app, run static checks and optional Radon complexity (matches Makefile and Cursor post-write hook intent).
- ▌ Specflow Usability Check · griddynamicsAssess how SpecFlow can be applied to a potential customer based on their specs, requirements, screenshots, and descriptions. Produces a sliding-scale fit report — always finds an angle of use, lists enablers and feature requests where needed, and only declares rejection when truly nothing fits.
- ▌ Specflow Analysis · griddynamicsAnalyze spec completeness locally — gap detection across all architectural dimensions. No backend required. Repeatable as specs evolve.
- ▌ Specflow Diagnose · griddynamicsDiagnose errors and symptoms from a SpecFlow-deployed app. Collects observables (logs, error messages, infra state), identifies root cause through guided discovery, and proposes fixes appropriate to each actor — SpecFlow agent re-run, operator intervention, or spec backport.
- ▌ Specflow Planning · griddynamicsCreate a phased implementation plan locally from specs and analysis output. No backend required. Produces IMPLEMENTATION_PLAN.md and optionally e2e-test-plan.md.
- ▌ Specflow Compare Variants · griddynamicsCompare and assemble code from 1–3 SpecFlow-generated workspace repos. Produces per-workspace inventory, a side-by-side comparison matrix, interactive component selection, and a concrete file-level assembly plan for migration to a production repo.
- ▌ Skill Name Must Equal The Parent Folder Name Of Skill Md Low · griddynamics bundleGENERIC form: To <verb> <what it does + when/why; dense keywords>. CRITICAL/guardrail form: 'Rosetta CRITICAL MUST skill. MUST activate when <condition>'. Budget: all skills share ~1K tokens — keep ≤ ~25 tokens and dense; over-long is ignored the same as terse, keyword-dense descriptions trigger best. EXCEPTION: disable-model-invocation:true => this description is actually user friendly.
- ▌
- ▌
- ▌
- ▌ Documentation · griddynamicsTo write, design, review, simplify, restructure, or standardize OSS project documentation
- ▌
- ▌ Compress Prompt · griddynamicsCompress a Rosetta KB prompt artifact (skill · workflow · phase · rule · agent · template · generic) by stripping structural tautology and ineffective scaffolding while preserving every importance-bearing token. Use when the user asks to compress, shorten, tighten, densify, or reduce a prompt / skill / workflow / phase / rule file.
- ▌ Hitl · griddynamics bundleMUST 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`.
- ▌ Update Change Log · griddynamicsTo synchronize CHANGELOG.md with changes made last week (mon - sun)
- ▌ Coding · griddynamics bundleTo implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.
- ▌ Design · griddynamics bundleTo decide architecture — alternatives, tradeoffs, committed decision with rationale, boundaries, domain-specific concerns.
- ▌ Backlog · griddynamics bundleTo validate story readiness for a sprint or to break work into a human WBS.
- ▌
- ▌ Harness · griddynamics bundleTo build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
- ▌ Rosetta · griddynamics bundleRosetta identifies and routes user request to the most matching workflow
- ▌ Testing · griddynamics bundleTo write thorough, isolated, idempotent tests — 80%+ coverage, external-only mocking, scenario-driven.
- ▌
- ▌ Planning · griddynamics bundleTo build execution-ready AI sessions graph with intent/ACs/checklists.
- ▌ Research · griddynamics bundleTo run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation.
- ▌ Security · griddynamics bundleRun authorized, evidence-preserving security reviews and prepare remediation inputs.
- ▌ Debugging · griddynamics bundleTo investigate errors, test failures, and unexpected behavior — root cause before fix.
- ▌ Deviation · griddynamics bundleMUST 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.
- ▌ Discovery · griddynamics bundleTo establish what exists — affected areas, behavior, prior attempts, dependencies, data.
- ▌ Reasoning · griddynamics bundleTo apply structured meta-cognitive thinking to complex problems. Invoke on explicit only.
- ▌ Solr Query · griddynamics bundleTo build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
- ▌ Tech Specs · griddynamics bundleTo define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
- ▌ Post Mortem · griddynamics bundleDiagnose instruction defects and optionally submit Rosetta GitHub issue
- ▌ Questioning · griddynamics bundleTo ask targeted clarification questions only when high-impact unknowns block safe execution.
- ▌ Solr Schema · griddynamics bundleTo design and audit Solr schemas: field types, analyzers, docValues, solrconfig.
- ▌ QA Knowledge · griddynamics bundleTo run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
- ▌ QA Structure · griddynamics bundleTo resolve QA session paths, identifiers/slugs, and state-file shape
- ▌ Specflow Use · griddynamics bundleTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
- ▌
- ▌ Aqa Flow · griddynamicsRouter workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
- ▌ Orchestration · griddynamics bundleTo delegate, prompt and manage subagents. MUST activate to spawn subagent with a quality prompt, unless trivial.
- ▌ Self Learning · griddynamics bundleMUST 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.
- ▌
- ▌ Sensitive Data · griddynamics bundleMUST 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.
- ▌ Solr Extending · griddynamics bundleTo build Solr plugins: SearchComponent, QParser, URP, DocTransformer.
- ▌ Adhoc Flow · griddynamicsWorkflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
- ▌ Data Collection · griddynamics bundleTo gather QA source artifacts from issue tracker, wiki, test management system
- ▌ Natural Writing · griddynamics bundleTo rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.
- ▌ Risk Assessment · griddynamics bundleMUST 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.
- ▌ Coding Flow · griddynamicsWorkflow for all coding: features, fixes, refactors, unit tests, etc.; scales small to large.