The prompt
Score 10 of 10, Excellent
Use it when A project or process involves several people and teams, and nobody is sure who decides, who does the work and who just needs to know.
- {{project_notes}}
- {{people}}
- {{project_name}}
Full prompt and why it works
Prompt
<project_notes> {{project_notes}} </project_notes> <people_and_teams> {{people}} </people_and_teams> <constraints> - Use only the people, teams and activities in the material above, with roles and team names as they appear there. - RACI meanings: Responsible does the work; Accountable makes the final call and owns the result; Consulted gives input before the decision or work; Informed is told afterward. - Each activity has exactly one Accountable. If the notes suggest more than one, or none, leave that cell blank and list the activity under "Needs a decision". - Do not give anyone a role the notes do not support. Where the notes are silent, leave the cell empty. - Keep Consulted short: only people whose input is actually needed, because a long Consulted list slows every decision. </constraints> <format> 1. A Markdown table: one row per activity or decision (8 to 20 rows), one column per role or team, with R, A, C or I in each cell. 2. Needs a decision: activities with no clear Accountable or with conflicting notes, each with the options. 3. Observations: up to 5 bullets, such as one person Accountable for too much, or an activity nobody is Responsible for. </format> <task> Based on the notes above, draft a RACI chart for {{project_name}}, for the project lead to confirm with the people named before it is shared. A good chart should be readable at a glance: anyone on the project can answer "who decides this?" from it. If anything is unclear about an activity, list your question at the end; do not guess. </task>
Variables
- {{project_notes}}
- Notes on the project or process: activities, decisions, meeting notes, chat threads about who does what.
- {{people}}
- The people and teams involved, one per line, with their role.
- {{project_name}}
- The project or process name.
Why it works
- What good looks like. Exactly one Accountable per activity is required, and a missing or doubled one goes to a Needs a decision list instead of being guessed.
- What to avoid. Cells stay empty where the notes are silent, so the chart shows real gaps instead of plausible assignments.
- Format. A grid plus a few observations, such as one person Accountable for too much, gives the lead something concrete to discuss with the team.