discovery

Guides multi-turn planning conversations to draft project-plan.md and build-plan.md files.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill discovery-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/discovery
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill discovery-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing detailed project and build plans from scratch is hard, and shallow plans lead to scope confusion later. This Skill runs an adaptive, one-question-at-a-time interview that draws out the problem, users, scope, technical constraints, and build order before drafting anything. ## Core Features & Use Cases - Adaptive Discovery Interview: Asks one focused question per turn, following consequential answers instead of a fixed questionnaire, with periodic snapshots of confirmed decisions, assumptions, and open questions. - Plan Drafting with Approval Gate: Drafts complete blueprint/project-plan.md and blueprint/build-plan.md contents only when the user asks, and writes the files only after explicit approval. - Existing Plan Preservation: Classifies existing plans as template, partial, or substantive, and preserves prior content and build-plan numbering when proposing changes. - Use Case: Before starting a new product, run the discovery conversation to think through MVP scope, non-goals, data model, and build order, then approve drafted planning files ready for the /overview step. ## Quick Start Ask the assistant to start a discovery session to think through your new product idea and draft the Blueprint project and build plans.

Frequently Asked Questions about discovery

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

FAQPage Schema
How do I create a project plan through a guided conversation?▼

Run the discovery skill and answer one focused question at a time about your problem, users, scope, and technical constraints. When you say you are ready, it drafts project-plan.md and build-plan.md for your review before writing anything.

What is the difference between project-plan.md and build-plan.md?▼

project-plan.md holds detailed rationale, constraints, edge cases, and decisions, while build-plan.md is a high-level numbered checklist of feature-sized outcomes ordered by dependency. The skill drafts both from the same discovery conversation.

Is discovery required before writing Blueprint plans?▼

No, discovery is always optional. You can write the plans manually or through any conversation and proceed directly to /overview; the skill never starts automatically from /onboard or because plans are empty.

Will discovery overwrite my existing project plans?▼

No. It classifies existing plans as template, partial, or substantive, summarizes what they establish, and preserves their content and build-plan numbering. It only writes files after showing proposed changes and receiving explicit approval.

When does the discovery conversation end?▼

It ends when the problem, users, MVP scope, technical choices, and build order are concrete, contradictions are resolved, and you explicitly say you are ready for drafts. There is no fixed question count.