opencode-smol

Full pipeline non-stop — plan, build every atomic task, review. No mid-pipeline pauses. Use when you trust the agent to take a feature from idea to reviewed implementation in one shot.

Execute the next pending atomic task from the latest plan in .smol/plans/, using strict TDD. Use after /smol-plan when stepping through tasks one at a time.

Skip planning. Apply TDD directly to a small change described in the prompt. Use for bug fixes, single-file edits, or trivial features.

Build or incrementally update the project codemap at .smol/. Run when starting on a new project, or after large refactors.

Turn a fuzzy idea into an atomic, TDD-ready task plan saved at .smol/plans/. Use whenever you want to "plan", "design", or "scope" a non-trivial change before implementing.

Review current git diff (staged + unstaged) for correctness, minimalism violations, and security. Use before committing, or pass a ref range to review past changes.

Create OpenCode plugins using the @opencode-ai/plugin SDK. Use for building custom tools, event hooks, auth providers, or tool execution interception. Use proactively when developing new plugins in .opencode/plugins/ or ~/.config/opencode/plugins/. Examples: - user: "Create a plugin to block dangerous commands" → implement tool execution before hook with blocking logic - user: "Add a custom tool for jira" → design tool schema and implementation using SDK context - user: "Show toast on file edit" → react to file edit events and display status message - user: "Build a custom auth provider" → implement auth flow for new model provider - user: "Intercept git commits" → add hook to validate commit messages before execution