stupidex

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.

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR or after completing a task.

Commit, push, and open a PR with an adaptive, value-first description. 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.

Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", or wants to commit staged or unstaged work.

Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", or "consolidate overlapping docs".

'Document a recently solved problem to compound your team's knowledge. Use when the user says "document this", "compound this learning", "what did we learn", or after fixing a bug.'

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says "debug this", "why is this failing", "fix this bug", "trace this error", or pastes stack traces, error messages, or issue references.

Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

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.

Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description.

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. 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.

Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.

Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use when the user says "simplify this", "clean up", or "refactor for clarity".

'Create or maintain STRATEGY.md -- the product\'s target problem, approach, users, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like "write our strategy" or "what are we working on" come up.'

Execute work efficiently while maintaining quality and finishing features. Use when the user says "implement this", "build it", "execute the plan", or provides a task description or plan document to execute.