Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Evaluate work for brag-worthy items and maintain a yearly brag document. Use when user wants to update their brag doc, review accomplishments, or when called from the recap skill. Supports standalone use, date ranges, and backfill from git/GitHub/Monday.
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Break a PRD into independently-grabbable vertical slices (tracer bullets) as linked Obsidian notes. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Generate an end-of-day recap summarizing work done across all Claude Code sessions. Use when user wants a daily summary, end-of-day notes, daily recap, journal entry, or daily log.
This skill should be used when the user asks to "review this branch", "review changes", "review the code", "code review", "review the diff", "check for issues", or wants a thorough code review of changes on any branch. Performs a deep, senior-engineer-level review that goes beyond surface-level checks.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Create a PRD through user interview, codebase exploration, and module design, then save as an Obsidian note. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.