using-agentops
Original:🇺🇸 English
Translated
Meta skill explaining the AgentOps workflow. Auto-injected on session start. Covers RPI workflow, Knowledge Flywheel, and skill catalog.
4installs
Sourceboshu2/agentops
Added on
NPX Install
npx skill4agent add boshu2/agentops using-agentopsTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →AgentOps Workflow
You have access to the AgentOps skill set for structured development workflows.
The RPI Workflow
Research → Plan → Implement → Validate
↑ │
└──── Knowledge Flywheel ────┘Research Phase
bash
/research <topic> # Deep codebase exploration
/knowledge <query> # Query existing knowledgeOutput:
.agents/research/<topic>.mdPlan Phase
bash
/pre-mortem <spec> # Simulate failures before implementing
/plan <goal> # Decompose into trackable issuesOutput: Beads issues with dependencies
Implement Phase
bash
/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
Validate Phase
bash
/vibe [target] # Code validation (security, quality, architecture)
/post-mortem # Extract learnings after completion
/retro # Quick retrospectiveOutput: ,
.agents/learnings/.agents/patterns/Phase-to-Skill Mapping
| Phase | Primary Skill | Supporting Skills |
|---|---|---|
| Research | | |
| Plan | | |
| Implement | | |
| Validate | | |
Choosing the skill:
- Use for single issue execution.
/implement - Use for autonomous epic execution (loops waves via swarm until done).
/crank - Use directly for parallel execution without beads (TaskList only).
/swarm - Use to gate/record progress through RPI.
/ratchet
Available Skills
| Skill | Purpose |
|---|---|
| Deep codebase exploration |
| Failure simulation before implementing |
| Epic decomposition into issues |
| Execute single issue |
| Autonomous epic loop (uses swarm for each wave) |
| Fresh-context parallel execution (Ralph pattern) |
| Code validation |
| Extract learnings |
| Full validation + knowledge extraction |
| Issue tracking operations |
| Root cause analysis |
| Query knowledge artifacts |
| Code complexity analysis |
| Documentation generation |
| Trace artifact lineage to sources |
| Trace design decisions through history |
Knowledge Flywheel
Every feeds back to :
/post-mortem/research- Learnings extracted →
.agents/learnings/ - Patterns discovered →
.agents/patterns/ - Research enriched → Future sessions benefit
Natural Language Triggers
Skills auto-trigger from conversation:
| Say This | Runs |
|---|---|
| "I need to understand how auth works" | |
| "Check my code for issues" | |
| "What could go wrong with this?" | |
| "Let's execute this epic" | |
| "Spawn agents to work in parallel" | |
| "How did we decide on this?" | |
| "Where did this learning come from?" | |
Issue Tracking
AgentOps uses beads for git-native issue tracking:
bash
bd ready # Unblocked issues
bd show <id> # Issue details
bd close <id> # Close issue
bd sync # Sync with git