pm

Convert the current Claude chat into a PMCollab spec document, open it in a Spec Review session with the Sphinx / Phoenix / Chimera reviewer agents, and file the work on the Code Factory queue so the pull request that delivers it can be handed back to the PM. Use when the user wants to "turn this conversation into a spec," "send this to PMCollab," "kick off a spec review," "create a change spec from this discussion," or runs `/pm:chat-to-spec-review`. Also use its Step 8 when the code for a spec this skill created has been pushed and the pull request needs submitting for approval. For a thin-context "just make this small change" request with no design discussion to harvest, route to `quick-change` instead — it edits first and captures the change spec behind the edit.

Turn the current Claude chat into a new PMCollab UseCase with its BXT detail bullets. Use when the user says "make this a use case," "add this to PMCollab as a use case," "create a use case for this," or runs the namespaced slash command /pm:chat-to-usecase. Walks pick-workspace -> distill chat into a draft -> ask follow-ups for missing essentials (title, problem, businessObjective, plus keyPersonas or valueProposition) -> confirm -> call usecase_create. Refuses with the existing id when a use case with the same title already exists. Companion to chat-to-spec-review, which assumes the use case exists.

Load a tight per-file extracted-facts pack for the code that backs a selected PMCollab use case via one MCP call (code_load_context). Use after select-usecase has resolved {workspaceId, useCaseId}, when another PMCollab skill says "load code context for this use case," or when the user says "pull down the code snapshot" / "load the related files." Returns one JSON object containing scan provenance (id, type, scannedAt, repoIdentifier), the matched extracted capability names, a per-file index of which business rules / AI prompts / MCP / A2A endpoints / change-log entries reference each file, and the full extracted artifacts scoped to the use case. scan is null when no completed scan exists. Returns extracted facts, NOT raw file bytes — calling skills should also Read the live local files for byte-level comparison.

Load a tight LLM-context pack for a selected PMCollab use case via one MCP call (usecase_load_context). Use after select-usecase has resolved {workspaceId, useCaseId}, when another PMCollab skill says "load context for this use case," or when the user says "pull down the use case context" / "load the spec for the selected use case." Returns one JSON object containing the use case essentials (title, description, status, detail bullets grouped by field, linked personas), every capability under it with its non-rejected behaviors compacted to {group, content}, and the CurrentSpec markdown (baseline creation spec + applied change specs collapsed) with its lineage and the baselineSpecDocumentId a change spec is authored against. currentSpec is null when not yet promoted.

Express path for small code changes — make the edit immediately, then capture it as a PMCollab CHANGE_SPEC as a byproduct (spec drafted from the diff, reviewers run async, commit stamped with a Change-Spec trailer). Use when the user asks for a quick, well-scoped change in a PMCollab-tracked repo — "just fix this," "quick change," "make this edit," "small tweak to X" — with little or no preceding design discussion, or runs `/pm:quick-change`. For changes that grew out of a rich design conversation, use `chat-to-spec-review` instead (see Routing).

Pick a PMCollab use case from a resolved workspace, with keyword filtering for large lists (100+ use cases). Use after select-workspace, when another PMCollab skill says "select a use case," or when the user says "pick a use case" / "scope this to a use case." Requires workspaceId (auto-chains to select-workspace if missing). Optional intentKeywords pre-filters the list. Returns useCaseId + useCaseTitle (both undefined if the user chose "none / leave unscoped").

Pick a PMCollab workspace for a downstream workflow. Use when another PMCollab skill delegates with "select a PMCollab workspace," when the user says "pick a workspace" / "switch PMCollab workspaces," or when a workflow needs workspaceId. Returns workspaceId + workspaceTitle. Identity (userId / email / displayName / tenantId) is auto-resolved by the pmc-mcp server from the authenticated connection — do NOT prompt the user for it. Use-case selection is a separate skill (select-usecase) — do NOT pick use cases here.

Reconcile spec-vs-code drift for one PMCollab use case. Loads the spec context (via load-usecase-context), the code context (via load-code-context), and the live repo files; emits a numbered drift findings list; for each finding proposes either "modify code to match spec" or "draft a CHANGE_SPEC to align the spec to the code"; executes the chosen action only after user confirmation. Use when the user says "align the spec for this use case," "check spec drift," "reconcile spec vs code," "is the spec out of date for X?" or runs the namespaced slash command /pm:spec-align.