ideate

Facilitate structured ideation to capture user intent, constraints, and success criteria.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill ideate-lleontor705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideate
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/ideate
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill ideate-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative ideation ensures user intent, requirements, and constraints are captured and aligned before any implementation, reducing rework and miscommunication.

Core Features & Use Cases

  • Structured dialogue and prompts to surface goals, constraints, and success criteria.
  • Explicit design gating with approvals, versioned design artifacts, and traceable decisions.
  • Works across projects from small enhancements to large system initiatives.

Quick Start

Describe your project goals and constraints, then approve a design before any implementation begins.

Frequently Asked Questions about ideate

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

FAQPage Schema
How do I capture design requirements before starting implementation?

To capture design requirements before implementation, use structured ideation to surface user intent, constraints, and success criteria. This process applies to projects of any size, from quick feature tweaks to end-to-end product initiatives, ensuring clear handoff to execution.

What is design gating and how does it prevent rework?

Design gating prevents rework by requiring explicit design approval and a persistent spec before any implementation begins. This formal review process ensures traceable decisions and versioned design artifacts, locking in the design to reduce miscommunication.

How do I facilitate structured collaborative ideation for a new feature?

Facilitate structured collaborative ideation by using guided dialogue and prompts to align user intent and constraints. This captures goals and success criteria early, requiring formal approval and documentation before moving to the build phase.

Can I use guided ideation for both small tweaks and large product initiatives?

Guided ideation works across projects of varying size, from small enhancements to large system initiatives. It ensures explicit design approval and a persistent spec regardless of project scale, satisfying requirements for gated design and formal review.

What is the best way to align user intent and constraints before a build phase?

The best way to align user intent and constraints before building is through structured dialogue that surfaces goals and success criteria. This creates a persistent spec and traceable decisions, ensuring formal review and clear handoff to execution.

Does structured ideation require formal approval before development starts?

Structured ideation requires explicit design approval before any implementation begins. This gated design approach ensures traceable decisions, versioned artifacts, and a persistent spec that satisfies formal review and documentation requirements.