tody-agent

Use when executing implementation plans — choose mode: batch execution with checkpoints, subagent-per-task, or parallel dispatch for independent problems.

Use when implementing any feature or bugfix, before writing implementation code

Use at end of sprint to append operational learnings as structured JSONL to the project retro log.

Use when exploring the CodyMaster skill ecosystem roadmap, marketplace, or distro validation.

You MUST use this before any creative work or multi-step task. Explores intent, requirements, and design before implementation. Then documents the plan before coding.

Working memory protocol — maintains context across sessions via CONTINUITY.md. Inspired by Loki Mode. Read at turn start, update at turn end. Captures mistakes and learnings to prevent repeating errors.

[Deprecated] discovery merged. Use `cm-skill-index` instead.

[Deprecated] skill lifecycle merged. Use `cm-skill-evolution` instead.

[Deprecated] parallel execution mode. Use `cm-execution` instead.

Use when running ANY terminal command - enforces clear progress logging, output reading, and error-stop behavior so terminal processes are never left unchecked

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Verify and lock project identity before ANY git push, Cloudflare deploy, or Supabase operation. Essential when working with multiple GitHub accounts (personal + work), multiple Cloudflare accounts, or multiple Supabase/Neon projects. Prevents wrong-account deploys, cross-project secret leaks, and git history contamination.