Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer lets-brainstorm first.
Document how an application works — its architecture, functionality, and business processes — as durable in-repo reference for teammates and contributors. Use when asked to 'document the architecture', 'write docs for this subsystem', 'explain how X works for the team', 'document our order/billing/auth process', or to produce onboarding docs people can read to understand the codebase. Name a topic for one focused doc, or omit one for a whole-app survey. Documents the system as it currently stands — not a change (lets-explain) or a solved problem (lets-compound).
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
Explain a change you didn't write — produce an orientation-first, teaching-depth walkthrough of a diff, PR, or commit range. Use when asked to 'explain this PR', 'walk me through this change', 'help me understand this diff', 'what does this change do', when getting oriented before reviewing, or when learning how a change works. Explains, does not critique.
Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.
Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.