Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

workflow-explore-idea

/workflow-explore-idea

Rozwija surowy pomysł w dojrzałe wymaganie gotowe do PRD przez wywiady sokratejskie, a na końcu uruchamia tworzenie PRD.

Licencja
MIT
Ostatnia zmiana repozytorium
31.08.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 31.08.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Rozwija surowy pomysł w dojrzałe wymaganie gotowe do PRD przez wywiady sokratejskie, a na końcu uruchamia tworzenie PRD.

Wyzwalacze z opisu

explore ideaI have an idealet
Oryginalny opis (EN)

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.

Jak działa

  1. Objective
  2. Exploration Phases
  3. Maturity Checklist
  4. Rules of Conduct
  5. Save Exploration Document
  6. Transition to PRD
Sekcje z nagłówków SKILL.md, w oryginale · 135 linii, 687 słów
Podgląd SKILL.md
---
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.

Wersje

W bazie nie ma innych skilli o nazwie workflow-explore-idea.

Migawka bazy z 13.11.2026 · wersja paczki 9d0befd9ad7d (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100write-prd
    Zamienia niejasny pomysł w ugruntowany PRD: wywiad z użytkownikiem, badanie bazy kodu i sokratejskie szkicowanie, z bramką wyjaśnień na końcu.
  • 100writing-vision-briefs
    Pomaga zamienić rozmyty pomysł w brief wizji biznesowej, który prowadzi do późniejszego PRD produktu.
  • 100idea-forge
    Przepuszcza surowy pomysł przez wieloetapowy potok R&D, który go interpretuje, rozwija, ocenia i zamienia w wykonalny plan inżynierski, uruchamiany od razu po słowie idea na początku wiadomości.
  • 100idea-forge
    Przepuszcza surowy pomysł przez wieloetapowy potok R&D, który go interpretuje, rozwija, ocenia i zamienia w wykonalny plan inżynierski, uruchamiany od razu po słowie idea na początku wiadomości.
  • 100prd-generator
    Tworzy lub aktualizuje PRD na podstawie plików idea.md i validate.md, bez zadań sprintowych i bez surowej walidacji pomysłu.
  • 100grilling-ideas
    Utwardza niejasny pomysł na funkcję, zanim powstanie PRD, specyfikacja lub zgłoszenie, wypytując o użytkowników, zakres i kryteria sukcesu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.