ideate

Generate a product specification document through iterative conversations.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/jaisonerick/spec-plugin --skill ideate-jaisonerick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideate
Source: https://github.com/jaisonerick/spec-plugin/tree/main/plugins/spec-plugin/skills/ideate
Command: npx skills add https://github.com/jaisonerick/spec-plugin --skill ideate-jaisonerick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Phase-based process helps teams quickly generate a complete product specification from a seed idea, reducing misalignment and rework.

Core Features & Use Cases

  • Seed the vision with guided questions to clarify problem, domain, and audience
  • Draft a structured specification covering problem, data model, pipeline, constraints, and success criteria
  • Refine the draft through iterative rounds and produce a specs/<project>.md document

Quick Start

Begin by answering Phase 1 questions with the user to seed the vision, then draft and refine the specification through iterative rounds.

Frequently Asked Questions about ideate

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

FAQPage Schema
How do I generate a product specification from a seed idea?

You generate a product specification by entering a guided dialogue that seeds the vision through questions, drafts structured sections covering problem framing and data modeling, and refines the document through iterative rounds.

What is the best way to document product management workflows for early-stage projects?

Documenting product management workflows is best done through a phased conversational process that seeds the vision, drafts the specification covering constraints and pipelines, and refines it to produce a versioned markdown document with frontmatter metadata.

Can I use conversational dialogue to create structured product specs?

Yes, you can use conversational dialogue to create structured product specs by progressing through seed, draft, and refine phases that systematically guide problem framing, data modeling, pipeline planning, and success criteria.

How do I frame problems and define success criteria for a new initiative?

To frame problems and define success criteria, you answer guided Phase 1 questions clarifying the domain and audience, then draft those details into a structured specification document covering constraints and pipelines for iterative refinement.

What format does the specification output use for versioned documentation?

The specification output uses a markdown file format at specs/<project>.md, incorporating frontmatter metadata and a phased workflow structure to ensure the generated product documentation remains reproducible and versioned.

Does this approach work for major initiatives or only early-stage projects?

This specification approach works for both early-stage projects and major initiatives, applying a phased seed, draft, and refine workflow to reduce misalignment and rework across various product management scopes.