discover

Conducts narrative discovery conversations to produce a discovery brief and process maps.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill discover-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/discover
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill discover-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a project without shared understanding leads to misaligned design and wasted build effort. This Skill runs a structured, story-based discovery conversation that turns a vague idea into a clear narrative brief, as-is and to-be process maps, and a defined design on-ramp before any design or planning begins. ## Core Features & Use Cases - Narrative Discovery Conversation: Explores four zones — who the user is, the journey, the moment of value, and what done looks like — with adaptive depth based on project complexity. - Process Mapping: Produces validated as-is and to-be process maps saved to docs/process/, establishing the process contract for all downstream phases. - Discovery Brief Output: Writes a concise narrative brief to docs/discovery-brief.md with key moments, open threads, out-of-scope items, and a design on-ramp decision (Figma import, reference-based, or from scratch). - Use Case: A solo builder has an idea for a booking tool. The Skill interviews them conversationally, maps the current manual process, drafts the target process, and produces a brief that feeds directly into the design sprint. ## Quick Start Start a discovery conversation for my new project idea and produce a discovery brief with process maps.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I run a product discovery conversation before designing?

Describe your idea at a high level and let the Skill guide a narrative conversation across four zones: who the user is, their journey, the moment of value, and what done looks like. It ends with a written discovery brief ready for a design sprint.

What is the difference between a discovery brief and a requirements document?

A discovery brief is a short narrative describing the user, their journey, and key moments, written for designers. A requirements document specifies system behavior for engineers. This Skill produces only the brief, never a spec.

Can I use discovery if I already have a Figma design?

Yes. The Skill explicitly supports projects with an existing Figma. The design on-ramp question at the end routes the next phase to use the Figma as source of truth while the discovery brief provides the story layer.

What are as-is and to-be process maps in product discovery?

The as-is map documents how the process works today, including manual steps and workarounds. The to-be map describes the target process once the product is built. Both are validated with you and saved to docs/process/.

When should I skip the discovery phase of a project?

Discovery should run first on any new project or feature, even simple ones. For clear, simple use cases the Skill adapts to a light depth of three to five questions rather than skipping the phase entirely.