Co Op Mission Planner

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 o...

Security Scan

The skill's code, instructions, and requirements are consistent with its stated purpose (text-only mission-planning guidance) and request no credentials or external installs.

Purpose & Capability

Name/description (co-op mission planning) match what the skill actually does: parse SKILL.md and return a descriptive guidance card. No unrelated credentials, binaries, or cloud access are requested.

Instruction Scope

SKILL.md is purely descriptive and explicitly states it will not create boards or send messages. handler.py only reads the local SKILL.md, formats sections, and returns text — it does not read other system files, access environment variables, or make network calls.

Install Mechanism

No install spec is provided. This is an instruction-only skill with a small local handler and test files; nothing will be downloaded or written to arbitrary locations during install.

Credentials

The skill declares no required env vars, credentials, or config paths. The code does not access os.environ or other credentials. Requested privileges are minimal and proportional.

Persistence & Privilege

always is false and the skill does not modify other skills or system settings. It can be invoked by the agent (normal default) but has no elevated persistent privileges.

Assessment

This skill is coherent and low-risk: it only reads its own SKILL.md and returns formatted guidance. If you want extra assurance, scan the included handler.py yourself (it’s short and readable) before enabling; also remember that the agent can invoke the skill autonomously by default — which is normal — but you should only enable skills you trust to run without network or credential access.

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.