kindle

Discovers requirements and produces an approved spec before any implementation begins.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill kindle-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kindle
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/kindle
Command: npx skills add https://github.com/Claudfather/clauDNA --skill kindle-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding on half-formed ideas, wasting effort on unexamined assumptions and building the wrong thing. This Skill enforces a structured ideation phase that turns a raw idea into a reviewed, approved specification before any code is written. ## Core Features & Use Cases - Guided discovery: Explores project context, then asks clarifying questions one at a time to pin down purpose, constraints, and success criteria. - Specialized lenses: Offers YC-style Office Hours questioning, architecture-aware Product Vision exploration, and gap-analysis Product Enhancement modes for different ideation scenarios. - Spec authoring and gating: Writes a contract-compliant decision document, self-reviews it for placeholders and contradictions, and blocks implementation until the user approves. - Use Case: You want to add a billing feature to your app. The Skill interviews you about scope and success criteria, presents a scaled design for approval, publishes a spec, then hands off to the planning skill. ## Quick Start Ask the assistant to run the kindle skill on your feature idea, for example: use kindle to help me scope a notifications feature before we build it.

Frequently Asked Questions about kindle

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

FAQPage Schema
How do I turn a feature idea into a spec before coding?

Run the kindle skill with your idea as input. It explores your project context, asks clarifying questions one at a time, presents a design scaled to complexity, and writes a decision-type spec that you must approve before implementation starts.

What is the ideation phase in a planning pipeline?

The ideation phase discovers what to build and whether it is worth building, producing an approved spec. In this pipeline, kindle handles discovery, then hands the spec to forge for planning, ironclad for adversarial review, and build for implementation.

Can I skip the design approval step for small changes?

No. The approval gate applies to every change, but its depth scales: a trivial change needs only a one-sentence design and a quick yes, while substantial work runs the full discover-to-spec pipeline. Deadlines justify a smaller gate, never zero approval.

When should I use product-vision instead of kindle?

Use product-vision when you want an on-demand, codebase-driven opportunity scan that is not gated on active creative work, including GitHub Issues output and auto mode. Use kindle when you have a specific idea to shape into an approved spec.

What happens after the spec is approved?

The spec status flips from draft to ratified, and the skill hands off to forge, passing the published spec path as input. Kindle never invokes implementation skills directly; forge coordinates hardening via ironclad and building via build.