hitl

Solid

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.

AI & Automation 295 stars 57 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Invoke as <hitl> <core_concepts> - "WHY" loop: idea → requirements → working software → learn → evolve - "HOW" loop: specs → code → tests → stories → features - Human gatekeeps every artifact in HOW loop. Good: human judgement breaks agent spirals fast. Bad: human becomes bottleneck, review time can exceed generation savings. - Internal quality matters not for its own sake — messy code makes agents spiral, costing time and money, resulting in bad UX of product. - Intermediate artifacts (code, tests, designs) are means to an end, not deliverables. - When output is wrong, fix the harness — not the artifact - YOU MUST FOLLOW HITL even if in `danger-full-access` or approval policy `never` or default mode or similar. - The cost of mistakes is VERY HIGH, assumptions are the top contributor — show to user for prior approval - When `dangerous-actions` hook denies a `reconsider`-tier call, the AI may retry by appending `# Rosetta-AI-reviewed` after reconsidering blast radius. For `hard-deny` patterns, human approval is required before any equivalent action. See the `dangerous-actions` skill. </core_concepts> <process> Questioning: 1. Ask until assumptions, ambiguities, gaps, conflicts resolved. 2. Skip LOW or NIT PICKING. 3. Prioritize: scope > security/privacy > UX > technical. 4. 5-10 targeted MECE questions per batch. 5. One decision per question. 6. Include why it matters and safe default. 7. Group related questions into a single interaction. 8. Track open questions using t...

Details

Author
griddynamics
Repository
griddynamics/rosetta
Created
4 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

questioning

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

295 Updated today
griddynamics
AI & Automation Listed

ratatoskr

Use on every user-facing turn, always — load it before you say anything to any user about this codebase or product. It is a standing discipline for how you communicate, not a tool tied to a particular activity; there is no turn on which you skip loading it. It governs change requests (feature, fix, refactor touching user-visible behavior, account management, data export or deletion, billing, payments, notifications, auth, retention, sharing, compliance like GDPR / PCI / HIPAA) and equally pure questions, explanations, code walkthroughs, and technical/user-visible translations. Plain-language discipline, the no-ceremony / no-machinery-names rule, no time or effort estimates, and question discipline apply on every turn without exception. Load it even when a written spec says implement verbatim, even for a pure internal rename, and even for an already-locked fix — loading is free; the skill itself decides how light to keep the turn, escalating to confirmation gates only when an operation is destructive, irrevers

0 Updated 4 days ago
krzysztofdudek
AI & Automation Listed

effective-interact

Load when agent pauses to report relatively complex information needing Chinese-first clear complex communication, alignment, multi-option choice, status/incident, long-task fact ledgers, implementation plans, reviews, maps, explainers, evidence, risks, validation, or handoff; choose plain text/Markdown/visual Markdown/HTML by decision cost; do not load merely because answer is long; skip trivial chat/bundled apps.

2 Updated today
JasonxzWen