Command
Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
Structured non-code project and knowledge management for Claude Code. (Before Karpathy made this fashionable...)
Command
Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
Command
Plan and execute a batch of ops tasks continuously without user input. Combines /ops:batch-plan and /ops:batch-execute for end-to-end autonomous handling of many items in a row. Never for code changes. Do NOT invoke this yourself! Should only be invoked by the user.
Command
Create a batch of ops plans continuously without user input, storing any user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.
Command
Run both ops finders in parallel (tasks, opps) and brief you on what they found. Discovery only — no plans, no execution.
Command
Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.
Command
Plan and execute an ops task end-to-end. Use for research, strategy, content, and specs. Delegates to /plan for planning and /execute for execution. Never for code changes.
Command
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
Command
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
Command
Process external information into the ops repo's knowledge base. Drop files in .update/ or pass content inline. Use when you have new information (research, status changes, reference material, deliverables) to integrate into the project's structured knowledge system.
Command
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".