lenar-amirov/product-pipeline-public

lenar-amirov/product-pipeline-public

Skill Claude Code

A way to turn a vague request handed down by a manager or another stakeholder into a one-page problem statement.

lenar-amirov/product-pipeline-public

Skill Claude Code

A rehearsal that puts a product presentation under hostile questioning before a formal review, using the evidence behind its claims.

lenar-amirov/product-pipeline-public

Skill Claude Code

A guided thinking session for strategy questions and organisational decisions that are not yet defined as product initiatives.

lenar-amirov/product-pipeline-public

Skill Claude Code

A structured way to review a screen or mockup against the user problem it is meant to solve, then check common usability rules.

lenar-amirov/product-pipeline-public

Skill Claude Code

A method for planning how to test the riskiest assumption behind a proposed solution, using an A/B test or a cheaper preliminary test.

lenar-amirov/product-pipeline-public

Skill Claude Code

An intake process for turning a PDF or PowerPoint deck, spreadsheet, wiki page, or pasted figures into traceable evidence for product hypotheses.

lenar-amirov/product-pipeline-public

Skill Claude Code

A method for turning user-interview notes into coded observations, recurring patterns, and evidence-based conclusions.

lenar-amirov/product-pipeline-public

Skill Claude Code

Synthesises user signals from multiple research sources into a unified insight brief, reconciling conflicting feedback. Use when user has data from multiple sources, needs to "make sense of all this user data", "what are users really telling us", "synthesise our research", or has conflicting feedback from different…

lenar-amirov/product-pipeline-public

Skill Claude Code

A decision aid that examines the current state of a product initiative and recommends the one to three most useful next actions. It uses evidence, dependencies, deadlines, goals, and recent decisions.

lenar-amirov/product-pipeline-public

Skill Claude Code

Map of pipeline steps (0-19) and jobs with registry rules; detailed per-step instructions live in references/steps.md. Read this whenever the PM calls a pipeline command (/analyze-cjm, /validate-problems, …) or a job, then read the matching section of references/steps.md.

lenar-amirov/product-pipeline-public

Skill Claude Code

A skill for checking whether a launched product change reached its planned metric target. It compares the starting point, target, and actual result, then records what happened to the related hypotheses.

lenar-amirov/product-pipeline-public

Skill Claude Code

A problem-analysis method for breaking a product issue into separate, complete branches and testable explanations. MECE means branches do not overlap and together cover the whole problem; the pyramid principle puts the main conclusion first.

lenar-amirov/product-pipeline-public

Skill Claude Code

A guide for writing a Product Requirements Document, a structured description of what a product should solve and how it should work.

lenar-amirov/product-pipeline-public

Skill Claude Code

Guides the PM through an initiative alignment checklist — metric, baseline, target, stakeholders, success/kill criteria. Use before a gate, when the PM says "setup initiative", "set the target", "define success criteria", "align on goals", or when the coverage map shows Frame incomplete. NOT a prerequisite for…

lenar-amirov/product-pipeline-public

Skill Claude Code

A skill for comparing possible product solutions using an assumption map and ICE or SIF scoring. ICE and SIF are prioritisation methods that weigh factors such as impact, confidence, effort, or strategic fit.

lenar-amirov/product-pipeline-public

Skill Claude Code

Generates the strategic story connecting your roadmap to company goals in a form non-technical stakeholders can repeat. Also structures Gate presentation narratives with source-backed claims. Use when user needs to "explain the roadmap", "present strategy to leadership", "create a narrative for all-hands", "build…

lenar-amirov/product-pipeline-public

Skill Claude Code

Captures the system context a PM needs for feasibility — affected components, dependencies on teams/systems, constraining NFRs, integration risks — feeding PRD §9-10 and the dev estimate. Use with the dev lead at estimation time, or when the user says "system design", "architecture constraints", "what does this…

lenar-amirov/product-pipeline-public

Skill Claude Code

An implementation blueprint that translates product requirements into a shared plan for the development team. It describes what changes, how parts should behave, and how each requirement will be checked.

lenar-amirov/product-pipeline-public

Skill Claude Code

An analytics planning and analysis aid for defining user events and examining funnels. A funnel is the ordered path users take through a product, such as viewing a page, starting checkout, and completing payment.

lenar-amirov/product-pipeline-public

Skill Claude Code

A guide for choosing interface patterns based on the user problem a proposed solution must address. A UI pattern is a familiar way of arranging an interaction, such as inline editing or a contextual banner.

lenar-amirov/product-pipeline-public

Skill Claude Code

A guide for creating user personas: practical profiles of groups of users based on research, behavior, goals, and problems.

lenar-amirov/product-pipeline-public

Skill Claude Code

Transforms requirements into user stories with Given/When/Then acceptance criteria ready for sprint planning and Jira. Use when user needs to write user stories, create Jira tickets, define acceptance criteria, or says "user stories", "acceptance criteria", "sprint backlog", "Jira tickets", "as a user I want"…

lenar-amirov/product-pipeline-public

Skill Claude Code

A user-research planning aid with a quick concept test and a full usability study. A concept test checks whether people understand and want an idea; a usability study checks whether they can complete tasks with it.