#66 Refactor: split fleet skill out of PM skill into a dedicated skill

[Anonymous]

Originally created by: kumaakh

Problem

The current pm skill bundles both PM orchestration logic and fleet tool usage guidance into a single skill. Agentic systems loading this skill receive conflicting signals — the PM role (planning, delegating, reviewing) is mixed with fleet operation mechanics (how to use MCP tools, member management, etc.).

This causes confusion in agentic contexts where:

• A non-PM agent loads the skill to use fleet tools but also absorbs unrelated PM workflow rules
• The PM skill grows bloated as both roles expand independently
• Agents running fleet operations are constrained by PM-specific rules that don't apply to them

Proposed Solution

Split into two separate skills:

1. fleet skill — Pure fleet tool usage: how to use MCP tools (register_member, execute_prompt, send_files, etc.), member management patterns, batching rules, background subagent requirements. No PM workflow, no sprint lifecycle.

2. pm skill — Orchestration only: sprint lifecycle, doer/reviewer loop, plan generation, progress tracking. Imports/references the fleet skill for tool usage but doesn't duplicate it.

Benefits

• Agents that only need fleet tool access load a focused, smaller skill
• PM skill stays focused on orchestration logic
• Reduces confusion for agentic systems trying to interpret which rules apply to them
• Easier to maintain and evolve each skill independently

Notes

• The pm skill can @fleet reference where needed
• Fleet tool descriptions in index.ts should remain provider-neutral (ongoing work in [#65])
• This is a skill-layer concern only — no changes to the MCP server itself

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed