claudecodex

rosetta-light

Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails. (lightweight profile: simpler workflows, smaller models)

375 on GitHubby Grid Dynamicsv3.1.27Apache-2.0updated yesterdayProductivity
/

Plugin rosetta-light from marketplace rosetta in griddynamics/rosetta. Commands read from the repo's manifest — yesterday.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (43)

  • backlog

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

  • checklist

    Session self-verification checklist

  • 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 panic, or user asked to UNDO.

  • 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` or `No HITL`.

  • 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 small task.

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

  • self-learning

    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.

  • self-organization

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

  • sensitive-data

    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 comp

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

  • subagent-directives

    MUST duties for a spawned subagent

  • tech-specs

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

  • testing

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

Subagents (10)

  • architect

    Architect solution, transform intent into reliable tech specs, etc. Full subagent.

  • discoverer

    Discover project context, patterns, affected areas, dependencies, etc. Lightweight subagent.

  • engineer

    Implement and test to high quality under the orchestrator-assigned identity. Full subagent.

  • executor

    Run simple commands, collect and summarize results to protect parent context. Lightweight subagent.

  • planner

    Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.

  • prompt-engineer

    Author and adapt prompts — discover, draft, deliver — under HITL approvals. Full subagent.

  • requirements-engineer

    Author, refine, and finalize requirements and specifications with traceability. Full subagent.

  • researcher

    Run deep research with grounded references, systematic exploration, self-validation, etc. Full subagent.

  • reviewer

    Review artifacts against intent and contracts, recommend, etc. Full subagent.

  • validator

    Validate that implementation matches intent via execution and evidence. Full subagent.

Hooks (3)

  • SessionStart

    printf '%s' '{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"<rosetta:plugin_files_mode REQUIRED=\"true\" OVERRIDABLE=\"FALSE\" PLAN_MODE=\"FULLY COMPATIBLE\" severity=\"CRI

  • SessionStart

    printf '%s' '{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"<rosetta:bootstrap_alwayson severity=\"CRITICAL\" use=\"ALWAYS\" compact=\"NEVER\" summarize=\"AS-IS\">\n\n<high

  • SessionStart

    printf '%s' "{\"hookSpecificOutput\":{\"hookEventName\":\"SessionStart\",\"additionalContext\":\"Rosetta Plugin Path: ${CLAUDE_PLUGIN_ROOT}\"}}"

View source on GitHub griddynamics.github.io

More from griddynamics/rosetta

All 4 plugins →

rosetta

claudecodex

Rosetta for Claude - Software Engineering Accelerator instruction set, workflows, and guardrails.

43 skills · 10 agents · hooks

375

Rosetta

codex

An instruction layer for AI coding agent

375

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

caveman

claude

Talk like caveman. Cut filler. Keep technical details explicit.

22 skills · 1 command · 3 agents · hooks

JuliusBrussee/caveman 119,462

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

Maintain rosetta-light?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins