team-tracking-mcp

Plugin team-tracking-mcp from marketplace team-tracking-plugin in RazvanRotaru/team-tracking-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (6)

• team-tracking-execute

  Use when you are a specialist subagent executing a single subtask (implementer, test-writer, adversarial reviewer, etc.). Covers acquiring the lock, recording a checkpoint after every git commit, the pulse-update protocol, and how to escalate work that's too complex back to the orchestrator instead

• team-tracking-obsidian-kanban

  Use when your project's team-tracking adapter is `obsidian-kanban` and you need to understand the file layout, card-eligibility rule, default-status rule, sub-bullet rendering, or auto-flip behavior. Reference for surprises that don't show up in `team-tracking-usage` because they're adapter-specific

• team-tracking-orchestrate

  Use when you are the orchestrator on a team-tracking project. Routes to the role-specific skill — `team-tracking-plan` (decomposing intent into board state, dispatching specialists) or `team-tracking-supervise` (keeping in-flight specialists on track via the event log and steering channel).

• team-tracking-plan

  Use when turning a goal/PRD into board state — reading the existing board, choosing hierarchy + priority, decomposing tasks into pipeline subtasks, and handing off to specialists. Covers what to put on the board and in what order. Pairs with `team-tracking-supervise` (after the dispatch).

• team-tracking-supervise

  Use when you have at least one specialist in flight on a ticket and you need to keep them on track — listening to the event log, reading checkpoints, posting nudges/questions, recovering from stale locks. Pairs with `team-tracking-plan` (which got you here).

• team-tracking-usage

  Reference for the team-tracking MCP server — the eleven tools, the four ticket types, the unified event log, the lock state machine, and the typed errors. Load this when you need to know what a tool does or how `lock_state` is derived. For role-specific protocols, use `team-tracking-plan` (planner,

Slash commands (3)

• /team-tracking-mcp:init

  Configure team-tracking-mcp for the current project (Jira or Obsidian Kanban).

• /team-tracking-mcp:reconfigure

  Replace the team-tracking-mcp config by re-running the init flow.

• /team-tracking-mcp:status

  Print the current team-tracking-mcp configuration (adapter, projects, lock TTL).

Subagents (1)

• team-tracking-planner

  Plans work for a team-tracking project. Reads the board, decomposes a goal/PRD into hierarchy + pipeline subtasks, creates the tickets, promotes parents to Todo, and returns a structured dispatch list. Use this for the planning phase only — supervision stays in the spawning session.

MCP servers (1)

• team-tracking

  runs: node ${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/index.js