
Use when a founder has a rough product idea and wants autonomous deep validation, market and competitor research, and an evidence-based MVP decision with minimal back-and-forth.
Use when deciding whether to split a coding task into parallel exploration, bounded review fan-out, or single-writer delegated work instead of keeping it in one agent.
Use when recently changed working code has become harder to safely modify after a feature, fix, or refactor, and needs a behavior-preserving simplification pass that improves readability, local reasoning, responsibility boundaries, and future editability without broad redesign.
Write and review Docker Compose files with consistent best practices and conventions (file naming, override strategy, service naming, key ordering, env handling, ports, and healthchecks). Use when creating or standardizing compose.yaml/docker-compose.yml.
Detect the repo's commit convention (Conventional Commits, Gitmoji, or a custom template) and create commits. Use when asked to commit, write a commit message, stage and commit changes, or commit and push work.
Use when investigating a repository that is not already available locally and the user needs repository-specific understanding of its structure, implementation, maintenance, or relevant files.