interserve

mistakeknot

Dispatch tasks to Codex CLI agents — single megaprompt for one task, parallel delegation for many. Includes structured debate triggers and Oracle escalation.

refactor-safely

mistakeknot

Use when performing significant refactoring — guides a disciplined process that leverages duplication detection, characterization tests, staged execution, and continuous simplicity review

engineering-docs

mistakeknot

Use when capturing a solved problem as categorized documentation with YAML frontmatter for fast lookup

landing-a-change

mistakeknot

Use when implementation is complete and all tests pass — guides the disciplined process of verifying, documenting, and landing a change on trunk

using-clavain

mistakeknot

Use when starting any conversation - establishes how to find and use skills, agents, and commands, requiring Skill tool invocation before ANY response including clarifying questions

executing-plans

mistakeknot

Use when you have a written implementation plan to execute in a separate session with review checkpoints

lane

mistakeknot

Manage thematic work lanes — discover, create, tag beads, show velocity and starvation scores

brainstorming

mistakeknot

Freeform brainstorming mode — loads collaborative dialogue style (one question at a time, multiple choice, incremental design). Use for open-ended exploration without structured phases. For a guided workflow with repo research, use /brainstorm instead.

upstream-sync

mistakeknot

Use when checking for updates from upstream tool repos (beads, oracle, superpowers, compound-engineering) or when the /clavain:upstream-sync command is invoked

galiana

mistakeknot

Show discipline analytics — defect escape rate, override rate, cost metrics, and agent scorecard

writing-plans

mistakeknot

Use when you have a spec or requirements for a multi-step task, before touching code

subagent-driven-development

mistakeknot

Use when executing implementation plans with independent tasks in the current session

dispatching-parallel-agents

mistakeknot

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

code-review-discipline

mistakeknot

Use when requesting or receiving code review — covers dispatching reviewer subagents, handling feedback with technical rigor, and avoiding performative agreement

using-tmux-for-interactive-commands

mistakeknot

Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys

file-todos

mistakeknot

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.