Claude Skills by gethamster

How to define MVP scope with MoSCoW: use the Must haves to draw the boundary of a first release, check it against what you need to learn, and hold it.

Run pivot or persevere decisions on a schedule: judge experiment evidence, know when to pivot a startup, and pick a pivot type that keeps what you learned.

Define Scrum roles and responsibilities the way the Scrum Guide does: one Product Owner, one Scrum Master and Developers, with clear decision rights.

Define the target market for an expansion strategy: turn a candidate new market into a precise, sized definition backed by evidence of demand.

How to define the customer experience before building: write the customer's journey through the finished product, then derive what to build.

Define waterfall model phases with entry and exit criteria, deliverables and owners, so each phase starts from an approved baseline.

Design assumption tests for solutions on your opportunity solution tree: surface hidden assumptions, map the riskiest, and test them with set criteria.

Design a competency-based PM interview with structured PM interview questions, a PM interview rubric and a hiring scorecard tied to Cabage's grid.

Design a content cluster architecture: scope the pillar page, list supporting pages, set URLs, and plan the internal links of a hub and spoke model.

Design a pain-focused interview guide for developer calls: a short, fixed question list built around the magic wand question and asked of every member.

Kanban board design: structure columns, swimlanes and cards so the board shows how work really flows from commitment to delivery.

Write a testable onboarding experiment hypothesis and pick primary, secondary and counter metrics in PostHog before an onboarding A/B test launches.

Design a product development strategy for current customers: find unmet jobs, test concepts and sequence them into a product development roadmap.

Build a 7 Ps marketing mix product strategy: define the core service, the elements around it and the differentiation the other six Ps must support.

Design customer retention strategies for the post-purchase stage: onboarding to first value, low-effort support, churn signals and renewals.

Role-based time allocation for business owners: turn a target Technician, Manager and Entrepreneur balance into protected weekly calendar blocks.

Design GIST step-projects as small, time-boxed experiments that test an idea's riskiest assumption and end in a clear continue, change or stop call.

Design usage-based pricing tiers for AI products: set boundaries, included usage and overage rates from real usage data and a margin floor.

Design validated learning experiments: pick the test, from landing page to concierge MVP or Wizard of Oz test, and set pass marks before any data arrives.

Develop your entrepreneurial vision in the E-Myth Entrepreneur role: write a primary aim, a strategic objective and a one-page vision for your team.

Diagnosing growth stalls with the four fits traces a plateau to the fit that broke, so the fix targets the cause instead of adding more tactics.

Create a Double Diamond diagram for your own project that shows its phases, activities, outputs and current position to stakeholders.

Differentiating PM roles on Cabage's competency grid: place consumer, growth, technical and platform PM role types by quadrant and set boundaries.

Drafting AI constitution principles: write the short critique, revision and comparison rules that steer Constitutional AI training.

How to write the external and internal FAQs of a PR/FAQ so they test the press release against customer doubts, costs, risks and open problems.

Run the RACE framework Act stage: build consideration stage content, landing pages and micro-conversions that turn visits into interactions and leads.

Write typography and spacing rules into a SKILL.md so AI coding agents choose type scale, line length, weight and rhythm on purpose.

Estimating reach for RICE means counting the people or events an idea will touch in one fixed time window, from product data or declared proxies.

Scrum estimation with story points and Planning Poker: size backlog items relatively, then treat velocity as a rough forecast and never a target.

Train, test and monitor the preference model that scores outputs against a constitution, so RLAIF optimizes the behavior you intended.

Evaluate buyer and supplier bargaining power by segment, using secondary data and primary market research for a supplier power evaluation you can defend.

Use Claude as a content optimizer: review drafts with a rubric built from the constitution's honesty traits and Google's people-first questions.

Evaluate a market penetration strategy by comparing pricing, promotion, distribution, retention and lead generation tactics in your current market.

Evaluating Market Product Fit means defining the market first, then testing whether the product earns retention and pull from that market.

Weigh Spotify model tradeoffs element by element, check each against known failure modes and pitfalls, and decide what to adopt, adapt or skip.

When to change your North Star Metric: spot the triggers, test a replacement against the old metric, and move teams, inputs and dashboards across.

Plan, timebox and facilitate a 4Ls sprint retrospective meeting so every person contributes and the team leaves with owned action items.

Facilitate a daily standup meeting that stays short, walks the board toward the sprint goal, and surfaces blockers early enough to act on them.

How to facilitate a design sprint: the design sprint facilitator keeps time, captures discussion, protects energy and hands decisions to the Decider.

Facilitate divergent ideation in the Double Diamond Develop phase: brainstorms, sketching and co-design that produce distinct solution concepts.

Plan and run an impact mapping workshop whose participants, preparation and detail fit its purpose: setting a vision, focusing delivery or reframing.

How to run a MoSCoW prioritization workshop with a neutral facilitator, prepared participants and ground rules, ending with an agreed priority list.

OST workshop facilitation: run an opportunity solution tree workshop that builds a first tree with your trio and brings stakeholders into discovery.

Facilitate a scrum retrospective that inspects how the Sprint went and ends with one or two owned improvements the team actually carries out.

Co-create a GO product roadmap with key stakeholders in a facilitated workshop, settle conflicts at the goal level, and reach consent on the plan.

How to run a start stop continue retrospective: prepare, review the facts, write in silence, group and vote, then leave with a few owned actions.

How to run a story mapping workshop: pick the right group, frame the problem, build the map together and leave with release slices everyone agrees on.

Run V2MOM workshops that move a leadership team or department from blank page to an agreed, ranked draft, with every voice heard before debate.

Squad formation for the Spotify model: write a squad mission statement, staff cross-functional squads, and launch autonomous squads that ship on their own.

Use a lean startup hypothesis template to turn vague business assumptions into falsifiable statements with a metric and pass mark set before testing.