Claude Skills by gethamster

Retrospective data gathering: the questions, techniques and prepared metrics that give a team one shared picture of the sprint before it explains anything.

Run the GIST planning ideas layer with a product idea bank: collect ideas from anyone, link each to a goal, triage quickly and park instead of delete.

Generate several candidate deliverables for each chosen impact, treat them as options, and pick the smallest slice that could cause the change.

Generate insights in a retrospective: cluster the sprint data, find patterns and use the 5 Whys or a fishbone to reach causes the team can act on.

Generate Claude AI long tail keywords from real user problems, then validate every idea with search data before you plan any content.

Generate multiple solutions for one target opportunity through individual ideation, then narrow to three for a compare-and-contrast decision.

Generate RLAIF preference labels: a feedback model compares two responses against a constitutional principle to build a reward signal.

Product backlog refinement, once called backlog grooming, splits, clarifies and sizes items so the top of the backlog is ready for Sprint Planning.

Find the specific people who can produce, obstruct, use or be affected by an impact map's goal, and choose which actors to focus on first.

Run cross-journey analysis to find cross-journey patterns, systemic pain points, and redundancies that single journey maps hide, then route them to owners.

Identify customer opportunities from continuous discovery interviews, framed in the customer's words and ready to place on your solution tree.

North star input metrics mapping: decompose your North Star Metric into a few input metrics that teams can own, test, and move week to week.

Find the minimum lovable requirements for a launch: trace each one to a promise in the PR/FAQ, cut the rest, and keep the headline benefit intact.

Surface the real obstacles to each V2MOM method with a premortem, write them precisely, and give the serious ones an owner and a response.

Find customer journey pain points and drop-off moments in each stage by pairing funnel data with interviews, tickets and session evidence.

Identify touchpoints across the four CDJ stages: inventory every interaction, tag who drives it, score its influence and find the gaps.

Identify underserved outcome opportunities: survey importance and satisfaction, compute Ulwick's opportunity scores, and read the landscape.

Build a story map backbone by finding the user activities in your product and arranging them in the order you would tell the user's story.

How to identify a North Star metric the framework way: surface beliefs, write the North Star statement, then choose the measure that fits it.

Implement AI self-critique and revision from Constitutional AI: a model critiques its own answer against a principle, then rewrites it.

Implement schema markup for answer engine optimization: JSON-LD that matches visible content, identifies your entities and sets honest expectations.

Implement a six pillar SEO strategy end to end: run mapping, anticipation, timing, deepening, scenarios and backcasting into one comprehensive SEO plan.

A gstack setup guide: the Claude Code installation, gstack slash commands setup, team mode, other agents, and fixes when skills do not appear.

Install Taste Skill SKILL.md files in Claude Code, Cursor, Codex and Gemini CLI, confirm the agent loads them, and keep local edits through updates.

Turn a prioritized impact map into a product roadmap sequenced by outcomes, then keep map and roadmap in step as impact measurements come in.

Run a PostHog experiment on Webflow and other marketing pages: install the JavaScript snippet, write variant code or use no-code web experiments.

Read PostHog experiment results under Bayesian or frequentist stats: win probability, credible intervals, p-values and what counts as significant.

Iterating a North Star metric through regular product metric reviews: check confidence, refine inputs and definitions, and know when to revise.

How to revise a PR/FAQ across rounds of review, from a solo draft to an executive decision, and how to tell when the document is ready to decide on.

Maintain a living opportunity solution tree: update it every few interviews and after each test so it stays the current record of discovery.

Run the change request process in a waterfall project: log each change, analyze its impact, take it to a change control board and update the baseline.

Manage gross margins on AI-powered features: track margin by feature and customer, set a floor, and act before heavy usage erodes profit.

Set the GIST planning cadence for each layer: yearly goals reviewed quarterly, an always-open idea bank, steps reprioritized each sprint, daily tasks.

Product backlog management: write user stories, prioritize the backlog, run backlog refinement, and prune it so the top is always ready to plan.

Managing projects with kanban: plan scope as options, pull work under WIP limits, and forecast delivery from throughput instead of fixed sprint plans.

Set up a Jira scrum board, map columns, run sprints and read the burndown and velocity charts, following Atlassian's own documentation.

Run a Shape Up six-week build cycle from kick-off to ship: protect the team's time, let it own scope, and use the circuit breaker when work will not fit.

Run design sprint day 1: set the long-term goal and sprint questions, map the problem, collect How Might We notes from experts and pick one target.

Map product management competencies on Neal Cabage's strategic-tactical and external-internal axes to build a PM competency framework for your team.

Map the complementary products force: list what customers use alongside your product, rate how necessary and healthy each is, and track who holds power.

Run an SEO baseline audit as pillar one of the six pillars: shared history, the futures triangle and the futures landscape applied to your site.

RACE funnel mapping: align each customer journey stage and touchpoint with Reach, Act, Convert or Engage, then find the gaps in your funnel coverage.

Map customer journey touchpoints in all five stages, including ones you do not own, and give each an owner, a purpose and a signal.

Write the impact level of an impact map: observable changes in each actor's behavior, helpful and hindering, that would move the goal, with ranges.

Use Double Diamond thinking to tell a team when to diverge and when to converge, and manage the switch between the two modes in every phase.

Mapping effort to person-months converts design, engineering and product estimates into one consistent RICE denominator that compares across ideas.

Map a few coarse-grained features to each goal on a GO product roadmap, check every one serves its goal, and move the detail to the backlog.

Map every growth initiative onto the Ansoff grid with clear definitions of new and existing, then read the portfolio balance to shape the marketing plan.

Research-intensive purchase mapping: build a customer decision journey map for a high-involvement purchase from buyer interviews and behavioral data.

Measure the initial consideration set: which brands buyers recall before they research, why yours is included or left out, and how to track it.