proposal-execution
Use when executing approved proposals. Researchers can execute ANY approved proposal (not just their own) to perform actions like memory cleanup, marking proposals ready for ticket/skill creation.
orchestrator-workflow
Coordinates agent assignments and manages ticket lifecycle.
memory-consolidation
Background process that proactively maintains memory hygiene. Scans for obsolescence to prune irrelevant data and synthesizes scattered information into higher-order patterns.
proposal-reviewer
Acts as a Contextual Analyst. Reviews pending proposals by checking the codebase to establish *plausibility* and *value*. Approves proposals where the code context supports the suggested improvements.
worker-workflow
Use for workflow guidance on HOW to work effectively. Covers task execution, decision escalation, and team coordination.
ticket-management
Use when creating or updating tickets. Covers ticket writing best practices, what to include, and what to avoid.
retrospective
Generate comprehensive learning documents by combining information from tickets, memories, GitHub PRs, and proposals. Use after completing significant work to capture lessons learned.
git-workflow
Use for any git operations: fixing PRs, creating commits, creating branches, pushing changes. Handles proper branch management, commit conventions, and stacked PRs.
memory
Use for knowledge sharing across sessions. Search memory before starting work, store memory after learning. Critical for avoiding repeated mistakes and maintaining context.