who-decides
FeaturedMap stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
DevOps & Infrastructure 948 stars
104 forks Updated yesterday MIT
Install
Quality Score: 90/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# who-decides
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
Map stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/who-decides.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
Details
- Author
- suboss87
- Repository
- suboss87/FDEOps
- Created
- 3 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
DevOps & Infrastructure Featured
what-breaks
Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
948 Updated yesterday
suboss87 AI & Automation Featured
debrief
Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.
948 Updated yesterday
suboss87 AI & Automation Featured
discover
Trace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.
948 Updated yesterday
suboss87