Menu
Meta skill explaining the AgentOps workflow. Auto-injected on session start. Covers RPI workflow, Knowledge Flywheel, and skill catalog.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Analyze code complexity and find refactor targets using radon/gocyclo. Triggers: "complexity", "analyze complexity", "find complex code", "refactor targets", "cyclomatic complexity", "code metrics".
Fully autonomous epic execution. Runs until ALL children are CLOSED. Level 1 uses /swarm (Task tool). Level 2 uses /spawn + Agent Mail for cross-session orchestration with Chiron help routing. NO human prompts, NO stopping.
This skill should be used when the user asks to "generate documentation", "validate docs", "check doc coverage", "find missing docs", "create code-map", "sync documentation", "update docs", or needs guidance on documentation generation and validation for any repository type. Triggers: doc, documentation, code-map, doc coverage, validate docs.
Extract decisions and learnings from Claude session transcripts. Triggers: "extract learnings", "process pending", SessionStart hook.
| name | using-agentops |
| description | Meta skill explaining the AgentOps workflow. Auto-injected on session start. Covers RPI workflow, Knowledge Flywheel, and skill catalog. |
You have access to the AgentOps skill set for structured development workflows.
Research → Plan → Implement → Validate
↑ │
└──── Knowledge Flywheel ────┘
/research <topic> # Deep codebase exploration
/knowledge <query> # Query existing knowledge
Output: .agents/research/<topic>.md
/pre-mortem <spec> # Simulate failures before implementing
/plan <goal> # Decompose into trackable issues
Output: Beads issues with dependencies
/implement <issue> # Single issue execution
/crank <epic> # Autonomous epic loop (uses swarm for waves)
/swarm # Parallel execution (fresh context per agent)
Output: Code changes, tests, documentation
/vibe [target] # Code validation (security, quality, architecture)
/post-mortem # Extract learnings after completion
/retro # Quick retrospective
Output: .agents/learnings/, .agents/patterns/
| Phase | Primary Skill | Supporting Skills |
|---|---|---|
| Research | /research | /knowledge, /inject |
| Plan | /plan | /pre-mortem |
| Implement | /implement | /crank (epic loop), /swarm (parallel execution) |
| Validate | /vibe | /retro, /post-mortem |
Choosing the skill:
/implement for single issue execution./crank for autonomous epic execution (loops waves via swarm until done)./swarm directly for parallel execution without beads (TaskList only)./ratchet to gate/record progress through RPI.| Skill | Purpose |
|---|---|
/research | Deep codebase exploration |
/pre-mortem | Failure simulation before implementing |
/plan | Epic decomposition into issues |
/implement | Execute single issue |
/crank | Autonomous epic loop (uses swarm for each wave) |
/swarm | Fresh-context parallel execution (Ralph pattern) |
/vibe | Code validation |
/retro | Extract learnings |
/post-mortem | Full validation + knowledge extraction |
/beads | Issue tracking operations |
/bug-hunt | Root cause analysis |
/knowledge | Query knowledge artifacts |
/complexity | Code complexity analysis |
/doc | Documentation generation |
/provenance | Trace artifact lineage to sources |
/trace | Trace design decisions through history |
Every /post-mortem feeds back to /research:
.agents/learnings/.agents/patterns/Skills auto-trigger from conversation:
| Say This | Runs |
|---|---|
| "I need to understand how auth works" | /research |
| "Check my code for issues" | /vibe |
| "What could go wrong with this?" | /pre-mortem |
| "Let's execute this epic" | /crank |
| "Spawn agents to work in parallel" | /swarm |
| "How did we decide on this?" | /trace |
| "Where did this learning come from?" | /provenance |
AgentOps uses beads for git-native issue tracking:
bd ready # Unblocked issues
bd show <id> # Issue details
bd close <id> # Close issue
bd sync # Sync with git