raci-check
Check and display the RACI responsibilities for any task, feature, or decision in the DreamTeam. Use when someone asks "who is responsible for X?", "who approves this?", "who do I need to consult?", "what is my RACI role?", or "show me the RACI for [task/feature/decision]". References the DreamTeam RACI matrix and Kanboard task metadata.
Informações da origem
- Repositório
- bivex/dreamteam
- Última atividade na origem
- 3 de março de 2026 às 15:54
- Idioma detectado do SKILL.md
- inglês
- Estrelas
- 0
- Forks
- 0
Opções de instalação
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Revise os arquivos de origem
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Exibindo SKILL.md
SKILL.md
Instruções da origem · Visualização somente leitura- name
- raci-check
- description
- Check and display the RACI responsibilities for any task, feature, or decision in the DreamTeam. Use when someone asks "who is responsible for X?", "who approves this?", "who do I need to consult?", "what is my RACI role?", or "show me the RACI for [task/feature/decision]". References the DreamTeam RACI matrix and Kanboard task metadata.
# RACI Check
Look up and display RACI responsibilities for a given task, feature, or decision type.
## How to Use
1. Identify the task type from the user's request
2. Look up the RACI matrix below
3. If a Kanboard task ID is provided, also query `get_task_metadata` for
task-specific RACI overrides
4. Return a clear breakdown of who does what
## DreamTeam RACI Matrix
| Task / Decision | Responsible (R) | Accountable (A) | Consulted (C) | Informed (I) |
|---|---|---|---|---|
| **Product Requirements (User Story)** | PM, PO, BA | PM | Dev, QA, Designer, PMM, DA | CPO, CSM |
| **Wireframes & Prototypes** | UX Designer | UX Designer | PM, PO, Dev | QA, CPO |
| **Technical Architecture** | Developer | Developer | PM, QA, BA | PO, CPO, ProjectM |
| **Feature Development** | Developer | Developer | UX Designer, QA | PM, PO, CPO |
| **Testing & Validation** | QA, Developer | QA | BA, ProjectM | PM, PO, CPO |
| **Release Decision** | QA | CPO | PM, PO, ProjectM, PMM, DA | Dev, Designer, CSM |
| **Technical Escalation** | Developer, QA | Project Manager | CPO, PM | Dev team |
| **Technical Documentation** | Developer | Developer | QA, BA | PM, PO |
| **Task Status Update** | Assignee | PO (sprint), ProjectM (project) | PM | CPO |
| **Legal Review of Feature** | Legal Counsel | CPO | PM, Dev, PMM, DA | PO |
| **User Agreements / ToS** | Legal Counsel | CPO | PM | All |
| **Product Positioning** | PMM | PMM | PM, CPO, CSM | Dev, QA |
| **GTM / Launch Plan** | PMM | PMM | PM, Growth, DA | Dev, QA, CSM |
| **Growth Experiments** | Growth Manager | Growth Manager | PM, DA, PMM | CPO, Dev |
| **KPI Definition** | DA | PM / CPO | Growth, CSM, PMM | All |
| **Customer Feedback Routing** | CSM | CSM | PM, PO | CPO, Growth |
| **Churn Risk Management** | CSM | CSM | PM, Growth, DA | CPO |
| **Sprint Planning** | PO, ProjectM | PO | PM, Dev, QA, Designer | CPO |
| **Daily Standup** | Project Manager | Project Manager | All active members | CPO |
| **Retrospective** | Project Manager | Project Manager | All team members | CPO |
| **OKR Setting** | CPO, PM | CPO | All leads | All team |
| **RACI Metadata on Tasks** | BA | BA | PM, PO | All |
## Output Format
```
🔍 RACI CHECK: [Task/Feature/Decision]
✅ RESPONSIBLE (does the work):
→ [Role]: [what they do]
🏆 ACCOUNTABLE (owns the outcome, signs off):
→ [Role]: [what they approve]
💬 CONSULTED (input required, 2-way communication):
→ [Role]: [what to ask them]
→ [Role]: [what to ask them]
📢 INFORMED (keep in the loop, 1-way):
→ [Role]: [how to inform them]
📝 NOTES:
[Any specific guidance or exceptions]
```
## Quick RACI Tags for Kanboard
When creating tasks, use these standard tags:
- `R-Responsible` — assigned to the doer
- `A-Accountable` — assigned to the sign-off person
- `C-Consulted` — mention in task description
- `I-Informed` — add to watchers/comments
Ver no GitHub