Interactively refine a feature idea through Socratic questioning before planning.
Refine a feature idea through structured critical thinking before it becomes a plan. This is a conversation, not a monologue — ask questions, wait for answers, push back, iterate.
Get the idea: Use $ARGUMENTS as the starting point. If empty, ask the user what they want to build.
$ARGUMENTS starts with #<number> (e.g. #42), invoke /fetch-issue first to load the issue as context, then brainstorm around it.Explore the codebase first: Before asking anything, use Read, Grep, and Glob to understand the relevant parts of the codebase. Ground every question in reality, not hypotheticals.
Run the brainstorm loop — repeat until the idea is solid:
a. Restate the idea in your own words to verify understanding. Expose any ambiguity.
b. Ask hard questions (2-4 at a time, not a wall of 10):
c. Wait for answers. Don't move forward until the user responds.
d. Push back when answers reveal:
e. Propose alternatives when you see a better path. Compare trade-offs concretely.
Spawn the brainstorm agent (via Task tool with subagent_type: Explore) if deeper analysis is needed — for example, when the feature touches many files and you need a thorough risk assessment before continuing the conversation.
Converge: When the idea is well-defined, produce a summary. Consider dosimex-site's constraints:
src/lang/fr.ts and src/lang/en.ts matching the ILang interfaceglobals.css, BREAKPOINTS/STYLE_CONSTANTS from src/types/styling.ts, inline CSS-in-JS with CSS.PropertiesuseIsMobile/useMobile/useTablet hooks for device detectionany types — use proper types or unknownpnpm test:run, pnpm lint:check, pnpm check-typesProblem: [What user problem this solves] Solution: [Concrete approach, grounded in the codebase] Scope: [What's in v1, what's deferred] Key decisions: [Choices made during brainstorm and why] Risks: [Remaining concerns to watch for during implementation] Ready for:
/create-issue <title> — to track this on GitHub/blueprint <one-line goal> — to plan the implementation(If an issue already exists from /fetch-issue, skip the /create-issue suggestion.)
src/Components/Navbar.tsx:45, this pattern suggests..."/blueprint is for/blueprint invocation