Agent skill
scenario
Author and manage holdout scenarios for behavioral validation. Scenarios are stored in .agents/holdout/ where implementing agents cannot see them. Triggers: "$scenario", "holdout", "behavioral scenario", "create scenario", "list scenarios".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/scenario-boshu2-agentops
SKILL.md
Scenario Skill
Author and manage holdout scenarios for Stage 4 behavioral validation.
Scenarios are holdout — implementing agents cannot see them (enforced by hook).
Evaluator agents validate code against scenarios during STEP 1.8 in $validation.
Execution Steps
Step 1: Initialize
ao scenario init # Creates .agents/holdout/ with README
Step 2: Author Scenario
Write a scenario JSON to .agents/holdout/<id>.json following schemas/scenario.v1.schema.json:
{
"id": "s-2026-04-05-001",
"version": 1,
"date": "2026-04-05",
"goal": "User can authenticate with valid credentials",
"narrative": "A user visits login, enters valid credentials, expects dashboard redirect.",
"expected_outcome": "Dashboard loads, session cookie is HttpOnly and Secure.",
"acceptance_vectors": [
{"dimension": "correctness", "threshold": 0.9, "check": "grep -q 'HttpOnly' headers"},
{"dimension": "performance", "threshold": 0.7}
],
"satisfaction_threshold": 0.8,
"scope": {
"files": ["src/auth/middleware.go"],
"functions": ["Authenticate"],
"behaviors": ["login flow"]
},
"source": "human",
"status": "active"
}
Step 3: Validate
ao scenario validate # Checks all scenarios against schema
Step 4: List
ao scenario list # All scenarios
ao scenario list --status active # Active only
Key Rules
- Scenarios use satisfaction scoring (0.0-1.0), not boolean pass/fail
- Scenarios should be written by humans or evaluator agents, NEVER by the implementing agent
sourcefield tracks provenance:human,agent,prod-telemetry- Agent-built specs (from
$implementStep 5c) useauto-*id prefix and live in.agents/specs/
See Also
$validation— STEP 1.8 consumes scenarios$vibe— Exposes satisfaction_score$implement— Step 5c generates agent-built specs
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?