ideation

Transform unstructured brain dumps into contracts, PRDs, and implementation specs.

113|12|Updated Nov 3, 2025

Search Tags:#documentation #ideation #specifications #contracts #brain dump #prds

Ready to run

npx skills add https://github.com/nicknisi/claude-plugins --skill ideation-nicknisi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ideation
Source: https://github.com/nicknisi/claude-plugins/tree/main/plugins/ideation/skills/ideation
Command: npx skills add https://github.com/nicknisi/claude-plugins --skill ideation-nicknisi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps turn unstructured brain dumps into structured, implementable artifacts (contracts, phased PRDs, and implementation specs) written to the docs directory for easy sharing and execution.

Core Features & Use Cases

Intake of scattered thoughts, transcripts, and dictated ideas.
Confidence-gated workflow: INTAKE → CONTRACT FORMATION → PRD GENERATION → SPEC GENERATION.
Auto-generated artifacts saved to ./docs/ideation/{project-name}/ for organized project setup.

Quick Start

Transform a raw brain dump into a contract, PRD, and spec for project "NovaTasks" and write artifacts to ./docs/ideation/nova-tasks/.

Frequently Asked Questions about ideation

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

FAQPage Schema

How do I turn unstructured notes into a product requirements document?▼

This Skill transforms scattered brain dumps, dictated ideas, and messy notes into structured PRDs by running them through a confidence-gated pipeline that enforces clarity at each stage—intake, contract formation, PRD generation, and spec generation—outputting ready-to-share artifacts to your docs directory.

Can I convert a brain dump directly into implementation specifications?▼

Yes. The Skill accepts raw, unstructured input—transcripts, scattered thoughts, topic tangents—and converts it through a phased workflow into contracts, PRDs, and implementation specs, all saved to ./docs/ideation/{project-name}/ with a 95% readiness threshold enforced.

What's the best way to document project ideas before building?▼

Structure your ideas using a confidence-gated process: intake messy notes, form a contract defining scope, generate a phased PRD, then produce detailed specs. This Skill automates that pipeline, asking clarifying questions as needed and outputting templated artifacts to keep documentation organized.

Do I need to clean up my notes before creating a specification?▼

No. The Skill is built to handle messy input—dictated streams, scattered notes, tangents—and structures them itself. It will ask you clarifying questions during the workflow to resolve ambiguities and ensure the final specs meet a 95% readiness threshold.

How does a confidence-gated workflow improve idea documentation?▼

A confidence gate ensures each stage—intake, contract, PRD, spec—reaches sufficient clarity before proceeding. This prevents incomplete or ambiguous ideas from becoming specs; the Skill prompts for clarifications and stops progression if confidence falls below 95%, protecting downstream implementation work.

Can I export my ideation artifacts to a specific directory structure?▼

Yes. All artifacts are written to ./docs/ideation/{project-name}/ using kebab-case directory names and established templates, making it easy to organize multiple projects, share with teams, and version-control your specs alongside your codebase.