mirror of
https://github.com/boshu2/agentops.git
synced 2026-09-14 15:08:13 +08:00
Boden Fuller
2b338ee0c3
Go fixes: - Fix UTF-8 boundary slicing in narrative truncation (rune-safe truncateRunes helper) - Add signal.Stop to rpi_serve signal handlers (prevent goroutine leak) - Replace CORS wildcard with localhost-only validation (prevent cross-site reads) - Surface SSE polling errors to client instead of silent continue - Extract section name constants (HISTORY/INTEL/TASK) from magic strings - Add intel_scope enum validation (none/topic/full) - Sort resolveSkillPath glob matches for deterministic resolution - Add random suffix to adhoc context IDs (prevent 1-second collision) - Surface writePromptAuditTrail errors to stderr unconditionally - Document RPI_RUN_ID env var in ao inject --help Doc fixes: - Replace stale /learn skill references with /retro --quick across 9 workflow docs - Replace .agents/retros/ with .agents/council/ in post-mortem SKILL.md + references - Reorder GOALS.md directives to sequential 1-8 numbering - Rename post-mortem Phase 2 steps from 4.x to EX.x - Update SKILL-TIERS.md: council + retro → council + knowledge lifecycle - Sync all changes to skills-codex mirror Epic: na-7r3 (6 issues, 2 waves)
2.5 KiB
2.5 KiB
name, description, estimated_time, phases
| name | description | estimated_time | phases |
|---|---|---|---|
| continuous-improvement | Ongoing system optimization and pattern refinement | Ongoing (periodic) | 4 |
Continuous Improvement Workflow
Purpose: Systematically improve system quality over time
When to use:
- Weekly/monthly reviews (extract learnings)
- After major milestones (retrospective)
- Pattern refinement (improve reusable patterns)
- Technical debt reduction (systematic cleanup)
Token budget: 30-50k tokens per cycle
Workflow Phases
Phase 1: Review (10-15% context)
↓
Phase 2: Identify (5-10% context)
↓
Phase 3: Prioritize (5-10% context)
↓
Phase 4: Improve (10-15% context)
Phase 1: Review
Goal: Assess recent work
Commands:
/retro --retrospective --since "30 days ago"
Activities:
- Review git commits
- Analyze patterns used
- Identify repeated problems
- Note what worked well
Output: Review summary
Phase 2: Identify
Goal: Find improvement opportunities
Activities:
- Code quality issues
- Documentation gaps
- Process inefficiencies
- Pattern opportunities
Output: Improvement candidates list
Phase 3: Prioritize
Goal: Rank by impact and effort
Matrix:
High Impact, Low Effort → DO FIRST
High Impact, High Effort → PLAN
Low Impact, Low Effort → MAYBE
Low Impact, High Effort → SKIP
Output: Prioritized improvement backlog
Phase 4: Improve
Goal: Execute improvements
Commands:
# For each improvement:
/plan [improvement]
/implement [improvement]-plan
/vibe recent
/retro --quick [improvement]
Output: Improved system + new patterns
Example: Monthly Improvement Cycle
# Phase 1: Review
/retro --retrospective --since "2025-10-01"
# Findings:
# - 15 commits reviewed
# - 3 patterns emerged (used 5+ times each)
# - 2 repeated issues (test failures, linting)
# Phase 2: Identify
# Opportunities:
# 1. Extract 3 patterns to pattern catalog
# 2. Fix recurring test flakiness
# 3. Add pre-commit hook for linting
# Phase 3: Prioritize
# Priority 1: Pre-commit hook (high impact, low effort)
# Priority 2: Fix test flakiness (high impact, medium effort)
# Priority 3: Extract patterns (medium impact, low effort)
# Phase 4: Improve
/plan pre-commit-hook
/implement pre-commit-hook-plan
/vibe recent
/retro --quick pre-commit-improvement
# Result: 90% reduction in linting issues
Start continuous improvement with: /retro --retrospective