brainstorm
Brainstorming Ideas and explore codebase
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
Anti-Pattern: "This Is Too Simple To Need A Design"
Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
Checklist
You MUST create a task for each of these items and complete them in order:
More from ouj/skills
rubber-duck
Collaborative design partner for coding problems, system design, bug fixes, and interface changes. Use when Codex should inspect the current project first, ask lettered multiple-choice questions one at a time, compare 2-3 clean solution approaches, draw before-and-after system interactions, and write a design doc before any implementation begins. Keep the focus on elegant interfaces and trade-offs, not production readiness, rollout, testing, or metrics.
10pr-stack
Manage stacked pull requests on top of plain git and GitHub CLI. Use when the user wants to create, inspect, restack, move, retarget, submit, or sync a stack of dependent branches and PRs while tracking parent branches explicitly, keeping each GitHub PR based on its recorded parent branch, and avoiding unsafe history rewrites.
8follow-my-lead
Finish an in-progress code change by reading the current git branch and especially the staged and unstaged diff to infer intent, then completing the implementation, migration work, interface changes, and repairs needed to make the change coherent. Use when the user already started work locally, wants the agent to pick up from the current branch state, wants intent inferred from unfinished edits, or wants plan-first collaboration with multiple-choice clarification before making changes.
4ask-me
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 "ask me questions".
3handoff
Compact the current conversation into a handoff document for another agent to pick up.
2