ideate

Propose 2–3 distinct solution approaches with trade-offs and risks.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/rockandrolla13/blueprint --skill ideate-rockandrolla13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideate
Source: https://github.com/rockandrolla13/blueprint/tree/main/ideate
Command: npx skills add https://github.com/rockandrolla13/blueprint --skill ideate-rockandrolla13

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams stress-test options and surface hidden assumptions before committing to an approach, reducing risk and rework later in the project.

Core Features & Use Cases

  • Structured divergence: generate 2–3 distinct approaches with clear trade-offs.
  • Assumption and risk synthesis: surface hidden assumptions and failure modes for early mitigation.
  • Convergence support: provide a recommended path and a plan for next steps to move to implementation.

Quick Start

Describe your problem and constraints, then ask for 2–3 structurally different approaches with trade-offs.

Frequently Asked Questions about ideate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm and compare different architecture approaches before committing to a design?

Architecture brainstorming is streamlined by generating 2–3 structurally distinct approaches, each with a brief description, key architectural implication, primary risk, and extensibility outlook to validate your solution. This structured divergence surfaces hidden assumptions and trade-offs early.

What is the best way to perform a risk analysis on a proposed software architecture?

Risk analysis is performed by identifying the core problem space and success criteria, then mapping the primary risk and load-bearing assumptions for each proposed approach. This process highlights failure modes and trade-offs to mitigate before implementation begins.

How do I choose between multiple design options and plan the first concrete artifact to build?

Choosing between design options is supported by a concise decision summary that outlines critical trade-offs, load-bearing assumptions, and the first concrete artifact to build. This convergence step moves you directly from architectural planning into implementation.

Can I use this for scaffolding a new project when I only have a rough problem description?

Yes, scaffolding a new project is supported when you provide a rough problem description and constraints. The process identifies the core problem space, proposes structurally different approaches with trade-offs, and outputs a recommended path with the first artifact to build.

When should I do a design review to surface hidden assumptions in my project planning?

A design review to surface hidden assumptions should be done early in project planning, before committing to an approach. Stress-testing your options at this stage identifies failure modes and load-bearing assumptions, reducing risk and rework later.

What are the limitations of relying on a single proposed architecture instead of generating distinct approaches?

Relying on a single architecture limits visibility into trade-offs, primary risks, and extensibility outlooks. Generating 2–3 structurally distinct approaches ensures you understand the architectural implications and hidden assumptions of the domain before implementation.