Claude Skills by gethamster

Structure customer opportunities into an opportunity solution tree hierarchy of parents, children, and siblings, the core of opportunity mapping.

Choose roadmap timeframes for a GO product roadmap: dates or quarters on internal plans, coarse horizons on external ones, and goals sized to fit.

Synthesize developer feedback from TAB calls into themes: pains, gains, and jobs per persona, outliers set aside, and a ranking checked with members.

Synthesize discovery findings into themes, insights and one agreed problem statement to define the problem in the Double Diamond Define phase.

Turn six force ratings into a narrative about the forces that dominate an industry and a short list of strategic options your team can act on.

Time content interventions for SEO pillars: read demand patterns, momentum and competitor moves to decide when to publish, refresh or retire a page.

Track AI search visibility with first-party reports and a fixed question set, measuring mentions, citations and share of citations over time.

Brand consideration tracking across the planned journey: measure which brands enter and leave the consideration set at each stage, and why.

Track developer sentiment across TAB sessions: one record per member and call, so you see how pain points and priorities shift over six months.

Track the Engagement and Retention parts of HEART with per-user engagement measures and cohort retention built from your behavioral logs.

Track innovation accounting metrics: set a baseline, pick actionable over vanity metrics, read cohorts and keep a scorecard that shows real progress.

Use a Shape Up hill chart to show each scope as uphill (still being figured out) or downhill (being executed) and track progress without status meetings.

Tracking retrospective action items: keep improvements visible, give them capacity, review them every retro and watch whether problems stop recurring.

Track 4Ls retrospective trends across sprints: log and tag themes and actions so recurring, systemic problems become visible and get fixed.

Decide which field-built solutions deserve to become product features, make the case with evidence, and hand them to the product team.

Plan an outcome-driven roadmap transition: move from a feature-based to an outcome-based roadmap in stages, keeping stakeholder trust along the way.

Move from journey mapping to continuous journey management: give priority journeys owners, live metrics, review cadences, and an improvement backlog.

How to emerge from technician to entrepreneur: hand off your technical work in stages and move the freed time into leading the business.

Translate features into benefits with a so-what chain that turns each product feature into a specific customer outcome and keeps the feature as proof.

Translate developer feedback from TAB calls into roadmap decisions: validated pains, the improvement that matters, and a story in members' words.

Learn breadboarding product design and fat marker sketching, so shaped solutions show flows and layouts at the right level of abstraction.

Claude Code constitutional guardrails for SEO scripts: pair Claude's intended behavior with permissions, tests and review so automation stays safe.

Use gstack's CEO, eng manager, staff engineer and QA lead roles, plus a second model through /codex, to examine one change from several angles.

A North Star framework roadmap: score bets by input influence and likelihood, prioritize by expected value, and review every finished bet.

Use start stop continue in a 1-on-1 or performance review: both people prepare items, talk through behaviors, and agree on one or two changes to review.

Use Working Backwards as a PM interview framework: answer product sense questions from the customer back, and prepare Amazon-style behavioral stories.

Test the two assumptions on each impact map branch, that a deliverable changes behavior and the change moves the goal, then prune or extend the map.

Validating Model Market Fit checks that your price, times the customers you can realistically win, adds up to the business you want to build.

Validate North Star metric choices with user research: ask customers what value they get, compare their words with the metric, and fix the gaps.

Turn recurring generic patterns in AI-built UI into named, checkable anti-slop rules with overrides, so agents catch them before code ships.

Write benefit-driven headlines that tell scanning readers what they gain, in their own words, and test them against clear feature-led alternatives.

Write clarity-first web copy: audit B2B website copy for jargon and vague claims, rewrite it in plain words, and check that visitors understand it.

Write a competency-based job description for a PM role from Cabage's grid, turning product manager responsibilities into clear PM hiring criteria.

Write desired outcome statements for each job step: direction, metric, object of control and clarifier, solution-free and ready to survey.

How to write OKR objectives: turn a strategic priority into one short, qualitative, concrete statement of what a team will achieve this cycle.

Write start stop continue feedback that works: specific, behavior-focused items with a situation and an effect, each one something a person could act on.

Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.

How to write an internal press release: the one-page working backwards press release that opens a PR/FAQ document before anything is built.

Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.

Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.

Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.

Keep your OODA cycles in step with a changing situation by time-boxing Orient, deciding provisionally and learning from every result.

Give AI agents persistent chat history and retrievable vector memory, then inject the right context into every model call.

Write explicit done, failure, budget, stall and approval rules before an agent loop runs, then apply them after every iteration.

Translate Boyd's OODA Loop into a working business loop with a clear mission, risk appetite, signals, decision rules and honest analogy limits.

Adapt the Four I's to the constraints of nursing, education, public service or business so the style works without depending on one leader.

Measure transformational leadership with the MLQ or similar surveys and interpret meta-analytic effect sizes without overstating what they prove.

Compare your site with the sites that outrank you to find missing topics, thin coverage and stale pages, then turn them into a ranked action list.

Build an always-on pipeline that finds, screens and schedules interview participants from your customer base so weekly discovery never stalls.

Evaluate candidate solutions against what people want, what technology can deliver and what the business can sustain, then decide trade-offs.