griddynamics/rosetta - Page 5

data-collection

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

debugging

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

deviation

CRITICAL. 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…

post-mortem

Diagnose instruction defects and optionally submit Rosetta GitHub issue

qa-knowledge

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

questioning

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

research

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

reverse-engineering

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

rosetta

Rosetta identifies and routes user request to the most matching workflow

self-learning

MUST 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.

self-organization

CRITICAL. MUST activate at 65%+ context usage, 2h / 15+ file / 350+ line scope, or large-file restructuring. Proactive planning, reorganization, stale-content cleanup.

sensitive-data

CRITICAL. 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,…

solr-extending

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

solr-query

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

solr-schema

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

solr-semantic-search

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

specflow-use

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

testing

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

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

research

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

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

debugging

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

post-mortem

Diagnose instruction defects and optionally submit Rosetta GitHub issue

questioning

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

research

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

rosetta

Rosetta identifies and routes user request to the most matching workflow

self-learning

MUST 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

CRITICAL. 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,…

specflow-use

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

testing

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

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

debugging

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

deviation

CRITICAL. 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…

post-mortem

Diagnose instruction defects and optionally submit Rosetta GitHub issue

questioning

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

research

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

rosetta

Rosetta identifies and routes user request to the most matching workflow

self-learning

MUST 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.

self-organization

CRITICAL. MUST activate at 65%+ context usage, 2h / 15+ file / 350+ line scope, or large-file restructuring. Proactive planning, reorganization, stale-content cleanup.