360 Secure SkillHub
360 安全技能中心

Co Op Mission Planner

帮助两人或多人把共同责任转化为合作任务:明确目标与完成条件,分配主导、支持、后勤等角色,拆分步骤并标注负责人、交接物与时间,加入同步检查点和掉线备份方案,最后给出降低冲突的对齐话术。纯文本输出,不创建真实任务看板或发送协作消息。

harrylabsj
harrylabsj
热度 33.03
最近更新 2026-06-06 05:10:43
分类:协作依赖:纯提示词应用场景:任务管理 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add co-op-mission-planner
Metadata
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

  1. Clarify the mission objective, finish line, and who is in the party.
  2. Map players into lead, support, logistics, observer, or cleanup roles when useful.
  3. Break the mission into steps with explicit owners, handoff items, and timing.
  4. Add sync checkpoints, fallback coverage, and what happens if someone drops offline.
  5. 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.