- name
- co-op-mission-planner
- description
- Turn a shared task into a co-op mission with clear roles, handoff points, sync rhythm, fallback coverage, and low-conflict alignment language. Use when two or more people need to coordinate a family task, study effort, or small project.
Co-op Mission Planner
Chinese name: 合作任务规划
Purpose
Help the user translate a shared responsibility into a co-op mission with visible roles, sequence, and backup plans. This skill is descriptive only. It does not create real task boards or send coordination messages.
Use this skill when
- Two or more people need to collaborate and responsibility feels fuzzy.
- The user wants cleaner handoffs in a family task, study partnership, or small project.
- Everyone assumes someone else will handle the next step.
- The user wants a gentler way to talk about roles without sounding bossy.
Inputs to collect
- Shared objective and what “mission clear” means.
- Participants, strengths, constraints, and availability windows.
- Known blockers, dependencies, and likely drop points.
- Preferred communication tone and sync frequency.
Workflow
- Clarify the mission objective, finish line, and who is in the party.
- Map players into lead, support, logistics, observer, or cleanup roles when useful.
- Break the mission into steps with explicit owners, handoff items, and timing.
- Add sync checkpoints, fallback coverage, and what happens if someone drops offline.
- End with a low-conflict alignment script the user can say out loud.
Output Format
- Mission objective with a clear win condition.
- Role assignment with who leads, supports, and closes.
- Co-op flow showing sequence, handoffs, and sync points.
- Risk and fallback notes for drop-offs, delays, or unclear ownership.
Quality bar
- Roles must be concrete enough that no one needs to guess ownership.
- Every important step should include a visible handoff object or confirmation point.
- Include at least one natural sentence the user can use to align without escalating tension.
- Keep the plan light enough for informal collaboration, not corporate process theater.
Edge cases and limits
- If collaborators do not actually share the same goal, address alignment before task splitting.
- If the relationship is sensitive, use softer phrasing and smaller commitments.
- Do not position this skill as a substitute for formal project management, contracts, or governance.
Compatibility notes
- Works for partners, families, friends, study buddies, and lightweight teams.
- Can pair conceptually with npc-dialogue-rehearser or quest-chain-decomposer.
- Text only, with no live board creation.