process

Featured

Process: retrospectives, session handoff, pair programming, subagent-driven development, condition-based waiting.

AI & Automation 425 stars 46 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Process Skill Five modes. Parse the request to pick one. Default to **retro** when ambiguous. | Signal | Mode | |--------|------| | Negative results, what didn't work, routing stats, review ROI, retro | **Retro** | | Hand off, package state, session pickup, rehydrate | **Handoff** | | Pair program, step by step, walk me through, one change at a time | **Pair** | | Subagent per task, execute plan, fresh context | **Subagent** | | Wait for, retry, backoff, poll, health check, circuit breaker | **Wait** | --- ## Mode: Retro Read-only retrospective. Two stores: `docs/what-didnt-work.md` (negative-results registry) and `learning.db` (routing/review telemetry via `scripts/learning-db.py`). ### Subcommands | Argument | Action | |----------|--------| | (none), what-didnt-work | Read `docs/what-didnt-work.md`. Group by date. Show each Decision verdict up front. If missing, report no negative results recorded. | | routing, route health | Run `python3 ~/.claude/scripts/learning-db.py route-health`, then `route-stats --by agent` (or the user's dimension). Present outcome basis before rates. | | reviews, review ROI | Run `learning-db.py review-roi` and `review-fps`. Present cost, findings, and false positives per agent in one table. | For comparisons: `learning-db.py route-delta --from SHA_OR_DATE --to SHA_OR_DATE`. --- ## Mode: Handoff Two submodes sharing one state contract. HANDOFF packages work for the next session. PICKUP rehydrates from that package. ### Handoff (endin...

Details

Author
notque
Repository
notque/vexjoy-agent
Created
6 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

agent-ops-retro

Retrospective on how the agents themselves are being operated, from local Claude Code transcripts plus the reports other jobs already produce. Answers what is going well, what is going wrong, what the human keeps having to repeat, and where delivery is leaking, then carries every unactioned finding forward with its age. USE THIS AUTOMATICALLY (no need for the user to name it) whenever the user asks to check all conversations, review agent usage, reduce the manual administration of agents, find repeating corrections or issues across sessions, audit skills and the knowledge ledger together, or asks what gaps exist in delivery over a recent window. This is the operator axis: for repository history and shipped work use retro-analysis, for a single finished change use wrap-up.

3 Updated today
oleg-koval
AI & Automation Listed

retro

Use when a Claude Code session ends or is declared finished, a friction needs fixing, a reusable learning needs capturing, local memory needs promoting upward, or for cross-session audits — detect friction AND learnings, route each to the right destination, and gate 'done'. Triggers: /retro, /retro done, 'retrospective', 'capture this learning', 'fix this skill', 'promote memory', 'audit', 'alles erledigt'.

7 Updated yesterday
netresearch
AI & Automation Listed

retro

Scientific session-closing retrospective: scan the current conversation, turn each signal into a falsifiable hypothesis, cite session evidence for AND against it, assign a verdict (supported / refuted / inconclusive) and a confidence level, then promote only supported, sufficiently-confident hypotheses into the harness memory tiers (.oh/memory/MEMORY.md, .oh/context/IDENTITY.md) behind a propose-then-confirm gate. Reflects on six learning/knowledge subsystems through the lens of this session — continual learning, context compression, reinforcement learning, wiki, docs, and memory scaffolding — and points at the deep-dive lint/audit skills rather than running them. Operationalizes the Memory Improvement Protocol (.oh/skills/retro/references/memory-protocol.md) as an explicit, evidence-driven, session-closing skill rather than a per-run afterthought. Always appends a log entry. TRIGGER when: /retro invoked, or session closing with decisions, surprises, or failures worth preserving.

40 Updated today
mifunedev