rosetta

Session self-verification checklist

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

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

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

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

Collect GitHub repo health/usage stats into merged JSON.

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, tighten, densify, or reduce a prompt / skill / workflow / phase / rule file.

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

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

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

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

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

Rosetta 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!

Classify workspace mode.

Discover tech stack.

Create agent rules.

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

To merge main branch, exact context and instructions

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

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