Manipulate Obsidian TaskNotes tasks, track time, run Pomodoro sessions, and search the vault via the obsidian CLI. Use when the user mentions tasks, task status/priority, time tracking, Pomodoro, vault search, follow-ups, or asks to capture a task.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Walk a human developer through implementing a plan or issue step by step, with active verification after each step. Use when the user wants to be guided through implementation instead of having the agent do it, or says "guide me", "walk me through", or "help me implement this myself".
Find deepening opportunities in a codebase, informed by domain language in CONTEXT.md and decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. Works in Pi and other agent harnesses.
Map an unfamiliar codebase, identify architecture, conventions, commands, entrypoints, dependencies, risks, and a safe implementation strategy. Use before non-trivial changes or when joining a new repository.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", or asks for integration tests.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a concrete implementation plan for immediate execution. Use when the user wants to plan quick implementation after a grilling session, or when saying "let's plan this" or "make a plan" for a change that doesn't need a full PRD.