Ideation FAQs

Question 1

What specific artifacts does this skill produce?

Accepted Answer

It generates a dedicated directory at `./docs/ideation/{project-name}/` containing a `contract.md` (defining goals and scope), phased `prd-phase-n.md` files for requirement sets, and `spec-phase-n.md` files which provide the technical implementation details for Claude to follow.

Question 2

What does the Ideation skill do?

Accepted Answer

The Ideation skill converts unstructured thoughts, messy notes, or raw voice transcripts into professional technical documentation. It automatically generates lean contracts, phased Product Requirements Documents (PRDs), and implementation specifications organized in your project directory.

Question 3

How does the confidence-gated workflow improve my project?

Accepted Answer

The skill uses a confidence rubric to assess your input's clarity across dimensions like problem definition and scope. By requiring 95% confidence before generating documents, it forces necessary clarifications early, preventing expensive misunderstandings during the coding phase.

Question 4

When should I use the Ideation skill?

Accepted Answer

Use this skill at the beginning of a new project or feature when you have a vision but lack a structured plan. It is particularly effective for processing 'stream-of-consciousness' ideas or dictated transcripts that need to be distilled into a technical roadmap.

Question 5

Can I use this with messy voice dictation transcripts?

Accepted Answer

Yes. One of the core strengths of the Ideation skill is its ability to process contradictions, tangents, and jargon-heavy rambling common in voice dictations. It filters out the noise to extract the technical signals needed for documentation.

Ideation

Ideation

Key Features

Use Cases

Key Features

Use Cases