Creates a structured implementation task breakdown for a structured change, synthesizing proposal, design, and specs into self-contained per-task files. Use when the tasks artifact is the next step in a change.
How to ask users questions interactively: which tool to use, how to batch questions, and when to ask serially. Follow this skill when asking clarifying questions, requesting confirmation, collecting missing requirements, or pausing for user input. Invoked by other skills rather than directly by the user.
Creates design artifacts through collaborative brainstorming of approaches, architecture, and trade-offs. Use when the user says "design this", "create a design", "brainstorm approaches", or "write a design doc".
Adversarial review of a proposal โ challenges the why, what, and how, and suggests alternative approaches. Use when the user says "review proposal", "challenge this proposal", "adversarial review", "poke holes", "stress test the proposal", or wants a second opinion on a proposal before moving to specs/design.
Evaluate whether a software idea is worth building, then write the proposal document. Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth building", or "should we build". If the idea passes evaluation, write the proposal document using the provided template.
Reviews risky/notable assumptions and context gaps surfaced by implementor session reports, fixes high-confidence issues directly, and asks one clarifying question at a time for ambiguous findings. Use when the user says "review assumptions", "audit implementor assumptions", or when invoked by a workflow's assumption-review step.
Reviews design artifacts (proposal, specs, design, tasks) for internal consistency, gaps, and cross-artifact alignment. Use when the user says "review spec", "review artifacts", "review the design docs", "review the change", or wants a quality check on proposal, spec, design, or task files before implementation.
Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design into one conversational pass, then writes tasks.md so the change is ready for implementation. Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for a change that doesn't warrant the full propose/spec/design ceremony.