stakeholder-map
/stakeholder-map
Mapuje osoby i role, na które wpływa praca, kto decyduje i kto może ją zablokować, wraz z postawą i powiązaniami.
- Autor
- SHOTClubhouse ↗
- Repozytorium
- shotos ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.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
Mapuje osoby i role, na które wpływa praca, kto decyduje i kto może ją zablokować, wraz z postawą i powiązaniami.
Oryginalny opis (EN)
Maps who is affected by a piece of work, who decides and who can block it, with goal, influence, stance and labelled links. Use when starting a change, project or deal. Roles only, not private profiles.
Jak działa
- Context and handoff
- When not to use this
- Steps
- Output
- Checks
Podgląd SKILL.md
--- name: stakeholder-map description: Maps who is affected by a piece of work, who decides and who can block it, with goal, influence, stance and labelled links. Use when starting a change, project or deal. Roles only, not private profiles. --- # Map the stakeholders Write down who is involved, what each one wants, and how you know. A map that mixes facts with hearsay is worse than no map, so every claim carries a label. **Stage:** Scope. **Rules:** 4 Claim only what you can show; 1 Stop at the boundaries. ## Context and handoff Read the project mandate and existing contacts. Verify who decides, who does the work and whose consent or input is required. Use `decision-brief` (from the exec-ops pack) when conflicting needs require a decision; if it is not installed, state the conflict, options and decision owner in the map. Save the map with the owning programme. ## When not to use this Skip it for a task that touches only you and one reader. A single line naming the reader is enough there. Do not use it to profile private individuals beyond their role in this work. ## Steps 1. **State the work in one sentence.** The map is always for a specific change, not for the organisation in general. 2. **List the people and organisations.** Sort them into three groups: affected (live with the result), deciding (can say yes or no) and blocking (can stop it without deciding it, such as legal, security, a budget holder or a supplier). One party can sit in more than one group. 3. **Resolve identity before joining records.** Treat two records as the same person or organisation only when two independent identifiers match, for example a work email domain plus a role on the company site, or a registered company number plus a postal address. A shared name alone is not a match. If only one identifier matches, keep the two records separate and mark the link `unresolved`. 4. **Record goal, influence and stance for each.** Goal: what they want from this work, in their words where you have them. Influence: high, medium or low, with the reason. Stance: supportive, neutral, sceptical, opposed or unknown. Write `unknown` rather than guessing. 5. **Label every link and claim.** Use exactly one label per line: - `confirmed`: the person or a primary document said it, and you can point to it. - `reported`: someone else told you, and you have not checked. - `proposed`: a suggestion about how things might be, not yet true. - `historic`: true once, not checked as current. Give the date. - `unresolved`: conflicting or incomplete; say what would settle it. 6. **Count events, not mentions.** The same conversation reported by two people is one event, not two confirmations. Note the original event and list the reporters under it. 7. **Name the gaps.** List who is probably missing and the single question that would find them. 8. **Stop at the boundaries.** Do not contact anyone on the map, and do not copy private details into it. Role, goal and stance are enough. ## Output Use [template.md](template.md). Save it with the work, for example `.work/<task>/stakeholders.md`. ## Checks - Every row has a goal, influence, stance and a label with its source. - No two records are joined on a name alone. - No claim reported by several people is counted as several confirmations. - Unknowns are written as unknown.
Pliki w paczce (3)
- README.md 3 KB
- SKILL.md 3 KB
- template.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · SHOTClubhouse/shotos | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
| qa-aman/claude-skills | 100 | MIT |
| veevia/design-agency | 100 | MIT |
| Sidsaladi9/persona-os | 100 | MIT |
| salesforce/salesforce-skills | 95 | Apache-2.0 |
| The-Utopia-Studio/skills | 90 | Apache-2.0 |
| tarunccet/pm-skills | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 4c794cf20bb8 (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
- 100persona-mapping
Mapuje interesariuszy między organizacjami macierzami Power-Interest, RACI, analizą wpływu i modelami salience, by ustalić, kto decyduje i jak z kim się komunikować. - 100davci
Określa jasne prawa decyzyjne: kto decyduje, kto zatwierdza, kto ma weto, kto jest konsultowany i kto informowany. - 90management-stakeholder
Mapuje interesariuszy według wpływu i zaangażowania, buduje macierz RACI, plan komunikacji i raporty statusu projektu. - 90who-decides
Mapuje interesariuszy, prawa decyzyjne, wpływy i blokady na podstawie dostarczonych dowodów, gdy własność jest niejasna lub krajobraz interesariuszy się zmienia. - 100soc-stakeholder
Prowadzi analizę interesariuszy: identyfikacja, klasyfikacja w macierzy władza-zainteresowanie i strategia wpływu, z planem komunikacji i zaangażowania. - 100okhp3-stakeholder-and-role-mapping
Tworzy rejestr interesariuszy z gotowego zapisu przyjęcia procesu, klasyfikuje role, ocenia wpływ i zainteresowanie oraz definiuje strategie zaangażowania.