mirror of
https://github.com/deanpeters/Product-Manager-Skills.git
synced 2026-09-14 20:06:57 +08:00
Dean Peters
27f739c582
Ten second-domain examples: - jobs-to-be-done, pol-probe, user-story-mapping, user-story-splitting (Northfield): two job performers who share a product and share no jobs; probes that are physical because you cannot ship a fake door to a plant floor; a backbone spanning days, sites, and organizations; and why the component split is especially costly when firmware release windows are infrequent - pestel-analysis, recommendation-canvas, company-research (Brightwater): Legal as the gating category rather than context; an AI line drawn on accountability rather than accuracy; and zero revenue read as a finding, not a red flag - product-sense-interview-answer: a diagnostic question, structurally opposite to the existing improvement question - the pair exists to teach that using the wrong shape is the failure mode - altitude-horizon-framework, executive-onboarding-playbook: career skills vary org shape, not industry. Horizon set by supply chain lead times; a product org that is not the company's main event Three Group A skills completed: - stakeholder-identification, stakeholder-mapping: templates plus both domains. Both examples land the most-affected, least-powerful group in Monitor on the first grid and correct it on the second, which suggests the mismatch is structural - skill-authoring-workflow: template plus one worked example (meta-skill carve-out), documenting a real build where Preflight nearly stopped it Plan 4 COMPLETE. Single-domain gap 21 -> 0 excluding the three documented carve-outs. Every Component and Workflow skill now ships a template and two-domain examples. Guardrail verified across all Brightwater files. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>