ideation

Clarify vague product ideas into testable concepts with structured lenses.

9|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/corca-ai/charness --skill ideation-corca-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideation
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/ideation
Command: npx skills add https://github.com/corca-ai/charness --skill ideation-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ideation helps clarify vague product, system, or workflow ideas by maintaining a living world model and separating verified facts from assumptions, accelerating early decision-making and reducing ambiguity.

Core Features & Use Cases

  • Build a living concept model that records verified facts, assumptions, open questions, and candidate directions to sharpen the overall concept.
  • Apply cross-disciplinary lenses (e.g., Daniel Jackson-style boundaries, Saras Sarasvathy-style effectuation, Donella Meadows-style systems thinking) to shape wedge, moat, and structure before committing to a spec.
  • Provide a clear path to spec when the concept is coherent, stable, and ready for execution.

Quick Start

Frame the concept, record verified facts and assumptions, and evolve the world model using the guiding references.

Frequently Asked Questions about ideation

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

FAQPage Schema
How do I turn a vague product idea into a testable concept?

Ideation clarifies a vague product idea by recording verified facts, assumptions, and open questions within a living world model, enabling you to test concepts and align stakeholders before committing to a spec.

What is the best way to align stakeholders across design, product, and engineering during early ideation?

The best way to align stakeholders is to apply cross-disciplinary lenses like systems thinking and effectuation to shape wedge, moat, and structure, ensuring design, product, and engineering teams share a coherent concept model.

How do I separate verified facts from assumptions when building a concept model?

You separate verified facts from assumptions by structuring early ideation sessions to explicitly record open questions and candidate directions alongside known facts, sharpening the overall concept model.

When should I move from a concept model to writing a spec?

You should move from a concept model to writing a spec when the concept is coherent, stable, and ready for execution, ensuring the living world model has successfully reduced ambiguity and aligned stakeholders.

Can I use systems thinking and effectuation to shape product wedge and moat before committing to a spec?

Yes, you can use systems thinking and effectuation to shape product wedge and moat before committing to a spec by applying these cross-disciplinary lenses to frame decisions and evaluate candidate directions.

Does ideation work for aligning teams on open questions and candidate directions?

Ideation works for aligning teams on open questions and candidate directions by enforcing a structured living world model that captures diverse perspectives and evolves them into a unified, testable concept.