need
/need
Zapisuje potrzebę biznesową lub problem opisany przez użytkownika, zakłada projekt i zadaje pytania rozpoznania.
- Autor
- MaiBP ↗
- Repozytorium
- professional-twin ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje potrzebę biznesową lub problem opisany przez użytkownika, zakłada projekt i zadaje pytania rozpoznania.
Argumenty
/need [description of the need]
Oryginalny opis (EN)
Captures a business need or problem the user describes, opens a project and starts discovery with questions. Use when the user describes a problem, an improvement opportunity or a request from their job.
Jak działa
- 1. Context
- 2. Open the project
- 3. Reply and ask
- 4. When to move to Definition
- Reference example
Podgląd SKILL.md
---
name: need
description: Captures a business need or problem the user describes, opens a project and starts discovery with questions. Use when the user describes a problem, an improvement opportunity or a request from their job.
argument-hint: "[description of the need]"
---
# New need → new project
The person describes a need in natural language (it may come in `$ARGUMENTS` or in the message). Turn it into a structured project.
Write in the language set in `settings.json` (`language`, default English), or in the language the person writes in. Labels and phase names follow the language of the project files: English files use "Current phase" and the phases Capture, Discovery, Definition…; Spanish files keep "Fase actual" and Captura, Descubrimiento, Definición…
## 1. Context
Read `profile/profile.md`, `profile/criteria.md`, `profile/goals.md` and `context/company.md`. Check `projects/` in case something related already exists (if so, propose continuing it instead of opening another one).
## 2. Open the project
- **If the project already exists** (the app creates it when the person tells a need, and tells you so), work in that folder: it already has the templates copied and the person's own account in the corresponding section of `00-need.md` ("Lo que contaste" in Spanish files). Adjust the title in `status.md` to a short, clear name if needed.
- If not, folder name: `projects/YYYY-MM-short-name/` (current date, name in lowercase with hyphens), and copy all of `templates/<lang>/project/` into it (`<lang>` from `settings.json`).
- Fill in the sections of `00-need.md`, keeping the headings the file already has (Spanish files: "Lo que contaste", "Lo que entiendo", "Primera lectura", "Relación con la proyección"):
- **The person's account**: the person's text, unchanged.
- **What I understand**: problem, who is affected, why it matters, symptoms.
- **First reading**: classify the initiative and list the solutions that usually work for this kind of problem according to good practice in the field (frameworks, standards, common approaches).
- **Link to the career path**: which skills from `goals.md` it lets the person demonstrate or develop.
- Fill in the **Summary card** in `map.md` with what you already know (the rest with ❓) and draft a first diagram of the current situation, how it is done today, if it can be deduced.
- Update `status.md` → Phase 1. Discovery (`1. Descubrimiento` in Spanish files) and mark `- [x] 0. Capture · YYYY-MM-DD` (`- [x] 0. Captura · YYYY-MM-DD` in Spanish files).
- If the person has existing documents, presentations or code, invite them to upload them in the project's **Material** tab in the app (`material/`), and read them before asking.
## 3. Reply and ask
Reply with:
1. **What I understood** in 3-5 bullets: the person corrects it if needed.
2. **How this is usually approached** in 2-4 lines: the typical approach, so the person sees where you are heading.
3. **First discovery batch** (3-6 questions): the ones that change the solution the most. For each one, a suggested answer.
Discovery topics depending on the case (pick the relevant ones; don't ask all of them):
- **Users**: who will use the result, how many, technical level, what decisions they make with it
- **Current situation**: how it is done today, what fails, concrete examples
- **Data**: sources, access, quality, frequency, possible exports
- **Definitions**: what each metric or concept means, whether the company has a standard
- **Success**: how we will know it worked, what would change day to day
- **Constraints**: allowed tools, deadlines, approvals, budget
- **Stakeholders**: who sponsors it, who can block it, who needs to be convinced
Record questions and answers in `01-discovery.md` as they come in.
## 4. When to move to Definition
When the critical questions are answered (✅) or explicitly assumed (🟡), propose: "I have enough to write the definition. Shall I go ahead?". Continue with `/advance`.
## Reference example
> "I'm in charge of telephony. Each manager looks at the metrics differently and interprets them according to what they think is right. Genesys Cloud doesn't offer good charts or clear definitions."
Expected first reading: a **KPI standardization + visualization tool** initiative. Typical approach: (1) an agreed metrics dictionary (AHT, ASA, service level, abandonment, FCR, occupancy…), with formula, source and threshold; (2) a single data source (Genesys Cloud API or exports); (3) a dashboard per audience (real-time operational, weekly tactical, monthly executive); (4) adoption: a session with managers and a review ritual. Initial questions: which metrics each manager uses today and with what formula, what decisions they make with them, what Genesys data can be accessed (API, exports, Performance Views), which BI tool is allowed, who must validate the definitions.
Wersje
W bazie nie ma innych skilli o nazwie need.
Migawka bazy z 13.11.2026 · wersja paczki 3e892d3b597c (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
- 90recipe-discover
Ujmuje szanse produktowe i tworzy istotne dla decyzji hipotezy z dostępnych dowodów, gdy bada się problem, szansę rynkową lub potrzebę użytkownika. - 100capture-the-problem
Zamienia notatki, skargę lub pomysł w opis problemu z osobami dotkniętymi, kosztem i najtańszym pierwszym testem. - 100po-create-user-story
Pisze historyjkę użytkownika z prostego opisu, sprawdza ją według INVEST i po potwierdzeniu zakłada w narzędziu PM. - 100problem-framing
Doprecyzowuje niejasny problem w bolączki użytkowników, przeformułowane pytania („jak moglibyśmy”) i uszeregowane szanse, zanim zaczną się rozwiązania. - 100np-school-teaching-needs
Ustala potrzebę technologiczną szkoły i problem dydaktyczny, zanim wybierze się sprzęt. - 100setup
Zakłada projekt lead-flow: zadaje cztery pytania o cel, repozytoria i odbiorców, sprawdza repozytoria i rejestruje hub.