// Open-ended thinking partner for vague ideas, hunches, and "what if" questions. Challenges assumptions, explores the codebase for evidence, searches the web for prior art, and keeps pushing the conversation forward. Never concludes on its own.
Create or update a GitHub PR for the current branch. It handles branch creation from main, rebases the full branch chain up to main, pushes with --force-with-lease, and generates a PR with a smart title and description focused on business rules and architecture changes. It can also screenshot the affected UI if the change touches frontend code.
Implement features and bugfixes using strict outside-in TDD. Each cycle traces back to requirements and design docs when available. It includes a deliberate refactoring phase and generates integration tests when a vertical slice is complete. It wires up BDD step definitions when feature files exist. It can receive a Linear issue as input, rebuilds docs (requirements, design, plan) from the issue into the repo before coding, and graduates them into permanent knowledge after the implementation is complete.
Create an implementation plan for an initiative. It references specific requirements and design decisions from docs/requirements/ and docs/design/, produces a plan in docs/plans/, and generates test cases traced back to requirements. It bridges "what to build" and "building it."
Record a "before/after" walkthrough video pair for a PR using Playwright. Trigger when the user asks to record a PR video, demo a fix, capture a UI walkthrough, or produce reviewer-facing media for a frontend or workflow change. Produces narrated mp4 (preferred for browser drag-drop into a PR description) and gif (committable to the repo so no browser is needed). Follows the team visual standard.
Split requirements, design specs, and plans into self-contained Linear issues targeting ~200-300 LOC each. It reads from the project's docs/requirements/, docs/design/, and docs/plans/, creates issues with the full spec embedded in the body, tags them with "agent issue", and creates an epic parent issue when more than two issues are generated. It deletes the repo docs files after the issues are created.
Review a PR or diff for architectural quality - SOLID principles, codebase consistency, dependency direction, error handling, data flow, test architecture, performance, and security. It reads the code review output for context, checks alignment with design docs, and produces actionable findings for the coding agent to fix.
| name | brainstorm |
| description | Open-ended thinking partner for vague ideas, hunches, and "what if" questions. Challenges assumptions, explores the codebase for evidence, searches the web for prior art, and keeps pushing the conversation forward. Never concludes on its own. |
| user_invocable | true |
| allowed-tools | Bash(git *), Read, Grep, Glob, Agent, AskUserQuestion, WebSearch, WebFetch |
| argument-hint | <a rough idea, hunch, or question, e.g., 'the GitHub client is doing too much' or 'should we use event sourcing for audit logs?'> |
An open-ended thinking partner. You bring a rough idea, a hunch, a frustration, or a "what if" - and this skill helps you explore it by challenging your assumptions, grounding the discussion in the codebase and the web, and keeping the conversation moving.
This skill produces no output files. It is purely conversational. It never wraps up, summarizes, or concludes unless you explicitly ask it to.
Argument: $ARGUMENTS
$ARGUMENTS and identify the core idea or question.After the user answers, do NOT wrap up. Instead:
If the conversation starts to feel like it is winding down or the user's answers are becoming shorter and more certain, do NOT conclude. Instead:
Only stop when the user explicitly says they are done.
Ask one question: "Do you want to take this into /requirements, /design-spec, or just leave it here?"
Do not summarize unless asked.