ideation_skill

Overview

This skill transforms messy brain dumps into structured, implementation-ready artifacts using a confidence-gated workflow. It guides intake, forms a lean contract, produces PRDs by phases, and generates detailed implementation specs for each approved phase. It enforces iterative clarification until confidence is high enough to proceed.

How this skill works

Start by ingesting whatever the user provides — notes, transcripts, tangents, or partial ideas. The tool analyzes inputs to extract problem, goals, success criteria, scope, and contradictions, then scores confidence across dimensions. If confidence is below threshold, it issues targeted clarifying questions using the AskUserQuestion tool and repeats until ≥95% confidence. Once validated, it creates a contract, phased PRDs, and phase-level implementation specs written to a project directory.

When to use it

• You have an unstructured brain dump, voice transcript, or rough notes to turn into a plan.
• You need a lean project contract before writing requirements or specs.
• You want phased PRDs that prioritize dependencies, risk, and value delivery.
• You require implementation specs detailed enough for engineers to implement without re-reading PRDs.

Best practices

• Always feed raw, unedited ideas — the intake accepts messy inputs.
• Never skip the confidence check; act on the rubric to decide question count.
• Use the AskUserQuestion tool for every clarifying or approval prompt — do not ask plain-text questions.
• Aim for a ≥95% confidence score before generating the contract and artifacts.
• Break scope into independent, valuable phases so each phase can ship and be validated.

Example use cases

• Convert a week of scattered meeting notes and voice memos into a lean contract and phased PRDs.
• Turn a founder’s rough product pitch into a validated contract and prioritized implementation specs.
• Organize a messy feature brainstorming session into clear success criteria and testable specs.
• Create phased rollout plans for a new capability, including technical file changes and validation commands.