Results for “brain”

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

Guides collaborative dialogue to turn ideas into fully formed designs and specs, exploring intent, requirements, and design before implementation.

Guides a structured requirements workflow from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Guides a structured requirements pipeline from topic intake through brainstorming, spec writing, planning, user review, SRS generation, validation, and improvement reporting.

Generates feature ideas from PM, Designer, and Engineer perspectives for initial product discovery of a new product.

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Creative discovery partner for ideation and concept shaping. Use when brainstorming, exploring product ideas, expanding vague concepts, comparing directions, finding opportunities, creative ideation. Triggers: 'brainstorm', 'product ideas', 'concept exploration', 'idea expansion', 'creative thinking', 'product discovery', 'what if', 'I have an idea'.

Loop feature-interviews over a brainstorm idea set and consolidate survivors into the roadmap

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Identifies common creative thinking anti-patterns and provides detection methods and alternatives.

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders.

Generates an IEEE 830 Software Requirements Specification from raw client input through structured brainstorming, gap analysis, and clarification rounds.

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking, producing a concrete one-pager.

Generates multiple app variations in parallel, each a distinct interpretation of a theme, then ranks them and presents a gallery.

Transforms vague ideas into structured, actionable concepts through guided divergent and convergent thinking, producing a markdown one-pager.

Simulates Bill Gates' cognitive framework, strategic thinking, and decision-making processes for analysis and problem-solving.

Generate three alternative OKR sets for a team, aligned with company strategy, to spark strategic discussion and planning.

Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments for a product or feature.

Design low-effort experiments to test product assumptions for an existing product, including prototypes, A/B tests, spikes, and other validation methods.

Generate new feature ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints, then prioritize the best five.

Treats rough ideas as competing organisms on an evolution island, scoring, selecting, crossing, and evolving them through structured rounds to surface the strongest concepts.

Design lean startup experiments (pretotypes) for a new product by creating XYZ hypotheses and suggesting low-effort validation methods like landing pages, explainer videos, and pre-orders.

Orquestrador do time Code New Project Agents do Reversa. Conduz o pipeline greenfield, partindo de uma ideia em linguagem natural e produzindo brainstorm, personas, PRD e specs SDD em `_reversa_sdd/`. Use quando o usuário digitar "/reversa-new", "reversa-new", "começar projeto novo", "criar projeto do zero" ou pedir para iniciar um produto greenfield. Não escreve código de aplicação, apenas specs.

Orchestrator for the pre-decision business-idea lifecycle — generate ideas, model them, evaluate them, validate them with customers, and only then hand off to product-soul / brainstorming. Routes through `idea-generation`, `business-modeling`, `idea-evaluation`, and `customer-discovery`. Load when the user asks to explore business ideas, find a startup idea, evaluate a venture, validate an idea, says "what business should I start", "should I build this", "is this a good business", "I have a startup idea", "evaluate this venture", "model this business", "validate this idea", "Mom Test this", "Lean Canvas this", "Business Model Canvas", "Value Proposition Canvas", "go/no-go on this idea". Pre-decision suite — once one idea is committed, hands off to `product-soul`. Does NOT design features (use `brainstorming`) or audit built products (use `reality-check`).

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories.

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', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also triggers when ce-ideate, ce-brainstorm, or ce-plan need upstream grounding and no strategy doc exists yet.

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

Expert Socratic discovery skill for exploring ideas, architecture decisions, and technical design before writing any code. Use this skill — proactively and always first — when requirements are vague, when the user is debating between technical approaches, when the problem is unclear, or when a design decision could have significant architectural consequences. Triggers on: "should we use X or Y", "help me think through", "I'm not sure how to approach this", "what's the best architecture for", "trade-offs between", "design before I code", "let's think through this", "I have an idea", "how should I structure", "help me design", "I want to build X but not sure how", "what approach would you recommend", "is this the right way to". Produces a validated design doc with 2-3 implementation options, trade-offs, and a recommendation. Always use before planning when the approach is not yet locked.