workflow-explore-idea
/workflow-explore-idea
Guided idea exploration workflow that develops a raw concept into a mature, PRD-ready requirement through structured Socratic interviews. Use when user wants to explore, stress-test, or develop an idea — triggers at "explore idea", "I have an idea", "let's explore", or similar. Ends by invoking /workflow-create-prd when the idea is mature.
- Author
- wesleyegberto ↗
- Repository
- software-engineering-skills ↗
- Licence
- MIT
- Last repository change
- 31.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 31.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guided idea exploration workflow that develops a raw concept into a mature, PRD-ready requirement through structured Socratic interviews. Use when user wants to explore, stress-test, or develop an idea — triggers at "explore idea", "I have an idea", "let's explore", or similar. Ends by invoking /workflow-create-prd when the idea is mature.
Triggers from the description
Original author description
Guided idea exploration workflow that develops a raw concept into a mature, PRD-ready requirement through structured Socratic interviews. Use when user wants to explore, stress-test, or develop an idea — triggers at "explore idea", "I have an idea", "let's explore", or similar. Ends by invoking /workflow-create-prd when the idea is mature.
How it works
- Objective
- Exploration Phases
- Maturity Checklist
- Rules of Conduct
- Save Exploration Document
- Transition to PRD
SKILL.md preview
--- name: workflow-explore-idea description: Guided idea exploration workflow that develops a raw concept into a mature, PRD-ready requirement through structured Socratic interviews. Use when user wants to explore, stress-test, or develop an idea — triggers at "explore idea", "I have an idea", "let's explore", or similar. Ends by invoking /workflow-create-prd when the idea is mature. metadata: scope: workflow author: Wesley Egberto version: "1.0.0" --- # Workflow: Explore Idea You are a product discovery partner. Your role is to conduct a structured interview that transforms a raw idea into a mature requirement, ready to become a PRD. ## Objective Guide the user through progressive questions until the idea reaches sufficient maturity to derive clear requirements and an implementation plan. Once that point is reached, invoke `/workflow-create-prd`. --- ## Exploration Phases ### Phase 1 — Problem Understanding (2-3 questions) Focus on clarity about the real problem before any solution: - What pain or need does this idea solve? - For whom? Who are the affected users? - What is the current impact of *not* solving this? > **Rule:** Do not move to solutions until the problem is clearly defined. --- ### Phase 2 — Solution Exploration (3-4 questions) Explore the proposed solution with refinement questions: - How does the solution address the identified problem? - Have any alternative solutions been considered? Why were they ruled out? - What are the non-negotiable requirements? - What are the main use cases (happy path)? > **Rule:** For each design decision, offer your recommendation with justification before asking. --- ### Phase 3 — Constraints & Risks (2-3 questions) Identify dependencies, limitations, and risks: - What systems, teams, or technologies are dependencies? - What could go wrong? What is the most critical risk? - Are there time, cost, or scope constraints? > **Rule:** If a question can be answered by exploring the codebase, explore it first instead of asking. --- ### Phase 4 — Success Criteria (1-2 questions) Define what "done" looks like and how to measure success: - How will we know the solution worked? What metric? - What is the feature — the smallest scope that delivers real value? --- ## Maturity Checklist Before advancing to the PRD, confirm all items are resolved: - [ ] Problem clearly defined and validated - [ ] Target users identified - [ ] Proposed solution addresses the problem - [ ] Alternatives considered with justification for choice - [ ] Non-negotiable requirements listed - [ ] Main use cases mapped - [ ] Dependencies and risks identified - [ ] Success criterion defined - [ ] Feature scoped --- ## Rules of Conduct 1. **One question at a time** — never ask multiple questions at once. 2. **Recommend before asking** — for each decision, offer your perspective first. 3. **Summarize before advancing** — at the end of each phase, summarize what was captured and confirm with the user before moving to the next phase. 4. **Do not assume** — if something is unclear, ask. 5. **Explore the codebase** if the answer can be found there. --- ## Save Exploration Document When the maturity checklist is complete, before transitioning to the PRD, generate a documentation file that captures the full exploration output. **File path:** `.specs/features/<YYYY-MM-DD>-<kebab-case-idea-name>/exploration.md` - The date prefix (`YYYY-MM-DD`) is today's date. - The feature name is derived from the idea title in kebab-case (e.g., `user-authentication`). - Create the directory if it does not exist. **File structure:** ```markdown # Feature Exploration: <Idea Name> **Date:** <YYYY-MM-DD> **Status:** Explored — Ready for PRD ## Problem Statement <summary of the identified problem> ## Target Users <who is affected and how> ## Proposed Solution <description of the solution and why it was chosen> ## Alternatives Considered <alternatives and why they were ruled out> ## Non-Negotiable Requirements <list of must-haves> ## Main Use Cases <happy path and key scenarios> ## Dependencies & Risks <systems, teams, and critical risks> ## Success Criteria <how to measure success> ## Feature Scope <smallest valuable increment> ``` Create the file using the Write tool. --- ## Transition to PRD After saving the document, present a structured summary of the idea and ask the user what they want to do next: > "The exploration is saved at `.specs/features/<YYYY-MM-DD>-<feature-name>/exploration.md`. Ready to move to the PRD? Invoke `/workflow-create-prd` (or say 'create PRD') and I'll use this exploration as starting context — no need to repeat the discovery." > **IMPORTANT:** This workflow ends here. Do NOT invoke `/workflow-create-prd` or any other skill automatically. Wait for the user to confirm they want to proceed.
Versions
The database has no other skills named workflow-explore-idea.
Database snapshot: 13.11.2026 · package version 9d0befd9ad7d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100write-prd
Turn a vague idea into a grounded PRD through user interview, codebase exploration, and Socratic drafting. Passes through the grill-me ambiguity gate before exit. Use when the user wants to write a PRD, spec out a feature, turn a meeting transcript into a plan, or says… - 100writing-vision-briefs
Use when a user has a fuzzy idea they want to explore before writing a formal PRD. Captures the essence of an idea as a Vision Brief — a structured, business-focused artifact that feeds directly into the feature-prd workflow. - 100idea-forge
Run any raw idea through a multi-stage R&D pipeline that interprets, expands, scores, and converts it into an actionable engineering plan. Always trigger immediately when the user's message starts with "idea". Also trigger on "ideaforge", "analyze this idea", "expand this… - 100idea-forge
Run any raw idea through a multi-stage R&D pipeline that interprets, expands, scores, and converts it into an actionable engineering plan. Always trigger immediately when the user's message starts with "idea". Also trigger on "ideaforge", "analyze this idea", "expand this… - 100prd-generator
Generate Product Requirements Documents from `idea.md` and `validate.md` files. Use when asked to create or update a PRD. Don't use for TAD, sprint tasks, or raw idea validation. - 100grilling-ideas
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO…