pm-method-build-trap

Check three signals: whether the team is measured by shipped feature count rather than outcomes, whether the roadmap is a dated feature list instead of outcomes to achieve, and whether requirements come from stakeholder requests rather than strategy and user problems. This Skill runs that self-check and identifies the first signal to fix.

The product kata is a repeating cycle: define the target outcome, assess the current condition with data, set the next measurable target condition, then identify obstacles and run the smallest experiment to validate. It replaces committing to full feature builds with iterative learning loops.

Use the four-layer strategy deployment: vision, strategic intent, product initiatives, and options or experiments. Each layer must answer what it serves in the layer above, producing an alignment map from vision down to concrete product actions.

It does not cover interview scripts or requirement slicing techniques, and it fits organizations with some scale that need strategy-execution alignment. Very early solo teams can simplify the four-layer deployment, and outcome metrics are hard to apply for platform, compliance, or infrastructure work.

This Skill addresses the organizational and strategic layer of why teams do useless work, using strategy deployment and the product kata. Teresa Torres-style assumption tests are a specific technique that plugs into the kata's experiment step, so the two complement rather than overlap.