rosetta

Verify init completeness.

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

To load the most current project context; MUST during prep.

To merge main branch, exact context and instructions

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

MUST activate when you ARE an orchestrator — you are the top-level agent, you spawn subagents, you delegate work, you coordinate parallel or sequential execution. Defines delegation quality, subagent dispatch, routing, review, and ownership protocol.

To build execution-ready plans from approved intent/specs with EARS, sequenced WBS, and HITL checkpoints.

Diagnose instruction defects and optionally submit Rosetta GitHub issue

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

To apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.

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, and when assessing environment risk level. SHOULD be invoked manually before any new environment interaction.

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.

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

Rosetta 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

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

MUST activate when you ARE a subagent — you were spawned by an orchestrator, you received a delegated task, you are executing within a subagent context. Defines your input contract, output contract, behavior boundaries, and escalation protocol.

To synchronize web site with changes made to local *.md files

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