griddynamics/rosetta

daily-oss

Batch processing issues, PRs, discussions, implementations, etc.

checklist

Session self-verification checklist

checklist

Session self-verification checklist

collect-github-stats

Collect GitHub repo health/usage stats into merged JSON.

compress-prompt

Compress 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,…

documentation

To write, design, review, simplify, restructure, or standardize OSS project documentation

merge-main

To merge main branch, exact context and instructions

sync-web-site

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

update-change-log

To synchronize CHANGELOG.md with changes made last week (mon - sun)

backlog

To validate story readiness for a sprint or to break work into a human WBS.

codemap

To generate, populate, and use a project codemap

coding-agents-farm

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

coding-agents-hooks-authoring

To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.

coding-agents-prompt-authoring

To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.

coding

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

dangerous-actions

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.

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.

design

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

deviation

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…

discovery

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

harness

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

hitl

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`…

large-workspace-handling

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

load-project-context

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

natural-writing

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

orchestration

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

planning

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

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.

qa-structure

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

questioning

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

reasoning

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

requirements-authoring

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

requirements-use

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

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.

risk-assessment

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

Rosetta identifies and routes user request to the most matching workflow

security

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