---
name: group-project-peacekeeper
description: "Splits a group assignment into owned pieces with hand-off dates and checkpoints, so one quiet teammate cannot sink the project, plus a first message that does not sound bossy. Use when a student group has a shared assignment due, nobody has started, and the work needs splitting fairly with checkpoints. Do not use for solo essays or a general study schedule. Related topics: Students, Planning, Collaboration."
---

# Group Project Peacekeeper

Splits a group assignment into owned pieces with hand-off dates and checkpoints, so one quiet teammate cannot sink the project, plus a first message that does not sound bossy.

## When to use

Use this skill when a student group has a shared assignment due, nobody has started, and the work needs splitting fairly with checkpoints. Do not use it for solo essays or a general study schedule.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Read the assignment and marking criteria and list the distinct deliverables, until every marked item belongs to exactly one piece.
3. Assign each piece one owner by matching strengths to tasks, until no person holds more than their share and every piece has a hand-off date.
4. Name a backup reader for each risky piece, until a single dropout never leaves a piece unread.
5. Set two checkpoints before the deadline, each with the specific artefact that must exist, until both can be checked yes or no.
6. Draft the first group message with the split and dates in a friendly tone, until it can be pasted into the chat as is.

## Inputs

- **The assignment** (longer free text)
- **Due date** (free text, e.g. "Date")
- **How many of us** (choose one: 2, 3, 4, 5, 6 or more)
- **What people are good at** (longer free text)
- **Assessed individually as well as a group** (choose one: Yes, No)

## Output

A table of pieces with owner, backup and hand-off date, the two checkpoints with their required artefacts, and a short ready-to-send first message.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Group Project Peacekeeper

Our group has a project due and everyone agrees it matters but nobody has started. Turn the assignment into a work split that survives one person going quiet.

- The assignment: {{The assignment}}
- Due date: {{Due date}}
- How many of us: {{How many of us}}
- What people are good at: {{What people are good at}}
- Assessed individually as well as a group: {{Assessed individually as well as a group}}

Break the assignment into pieces with one named owner each and a hand-off date, sized so no single piece is fatal if it slips. Pair each risky piece with a backup person who has read it. Add two checkpoints before the deadline and, for each, name the specific artefact that must exist by then (a draft, a slide deck, a data table), since vague check-ins get skipped. If individual assessment applies, make sure each person's piece is visibly theirs. Finish with the wording of the first group message, friendly and direct, so the person sending it does not sound bossy.

## Pitfalls

- Giving the least reliable person the critical-path piece, so one miss sinks the project.
- Setting checkpoints as meetings rather than artefacts, which lets people attend without producing anything.
- Writing a message that assigns blame instead of proposing a plan, which starts the argument you wanted to avoid.
