Restate a PM problem into a falsifiable, ratified problem-set artifact.
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill shape-dbc-oduffy
Please help me install this Agent Skill. Skill: shape Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/shape Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill shape-dbc-oduffy
The shape skill prevents misalignment by ensuring the EM and PM agree on what the real problem is (and what “solved” means) before any solutioning or architecture begins.
Use /shape to converge on the problem and obtain a PM-ratified problem-set before the system creates any implementation plan.
High-intent search queries and answers about installing and using this skill.
Problem scoping alignment requires a falsifiable problem restatement and iteration until a shared understanding exists. You must define scope boundaries, success criteria, and out-of-scope constraints to prevent engineering from misreading the target problem.
A falsifiable problem restatement reframes the target problem in PM vocabulary so its boundaries can be tested and validated. You need this when a PM has a target problem requiring confirmation of scope and out-of-scope constraints before any design decisions.
Requirements validation involves surfacing the single load-bearing PM-altitude uncertainty with the highest probability-weighted rework consequence. This forces articulation of the most critical scope boundary rather than tactical doubts to prevent invalidating the plan later.
Yes, this approach supports a structured handoff by producing a frozen, PM-ratified problem-set artifact. This artifact acts as a decision gate that chains directly into plan preparation without requiring any other skill invocation.
Skipping PM-EM alignment causes the EM to begin solutioning from a misread, leading to architectural rework. Without a ratified problem-set exit gate, planning proceeds on tactical doubts rather than a confirmed, falsifiable problem scope.
KaiNakamuraCreate or update .thoughts/problem.md with the task's problem statement.
solitasrohOrchestrate four PM agents to generate a PRD document.
nishantnaagnihotriCoordinate Gate 2 PRD handoffs and validation checks before design progression.
Handy369Convert ambiguous requirements into a structured spec with scope and success criteria.
