lenar-amirov/product-pipeline-public
Hook Claude Code
Runs when a session starts, executing scan-initiatives.py, status.py and validate-evidence.py via python3 (3 commands). From lenar-amirov/product-pipeline-public.
lenar-amirov/product-pipeline-public
Settings file Claude Code
Agent settings declaring 1 hook event (SessionStart).
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
Structured critique of a design against the hypothesis it was drawn for, plus heuristic evaluation — for step 9 and any mockup review. Use for "critique the design", "review mockup", "ревью макета", "что не так с UX", "heuristic evaluation", "оцени дизайн".
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
Designs the validation experiment for a solution's riskiest assumption — AB test parameters (MDE, sample size, duration, guardrails, decision criteria) or a cheaper pre-test. The engine of /design-ab-test (step 14). Use for "спланируй AB-тест", "design the experiment", "sample size", "MDE", "как проверим решение"…
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
First-class intake of external data the PM was given — a deck (PDF/PPTX), analytics export (xlsx/csv), Confluence page, or pasted numbers. Extracts key metrics with exact locations, maps them onto open hypotheses in the registry, proposes upgrades/refutations. Use when the PM says "мне принесли дек", "вот…
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
A method for turning user-interview notes into coded observations, recurring patterns, and evidence-based conclusions.
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
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 CodeCodex
Diagnoses the initiative state and recommends the 1-3 most valuable next actions. Use when the PM says "what's next", "что дальше", "continue", "где мы", "продолжаем", "what should I do", or seems unsure where to go — instead of mechanically suggesting the next pipeline step number.
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
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 CodeCodex
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 CodeCodex
MECE issue trees, pyramid principle and 80/20 prioritization for breaking a product problem into testable hypotheses — the structuring engine behind /hypotheses and /validate. Use for "разложи проблему", "issue tree", "MECE", "почему падает метрика", "structure this problem", "root cause".
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
Creates comprehensive Product Requirements Documents (PRDs) covering context, user segments, metrics, solution scope, and user stories. Use when user needs to write a PRD, document requirements, or says "write PRD", "product requirements", "product spec", "PRD structure", "requirements document", "написать PRD".
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
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 CodeCodex
Translates PRD requirements into an implementation blueprint agreed with the dev team — scope by component, behavior-level contracts, acceptance mapping, estimate structure. Use at dev-estimate time or when the user says "tech spec", "implementation spec", "спецификация", "технический документ". Complements…
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
Designs what to track and how to read funnels — event schema derived from open hypotheses, funnel/cohort analysis for validation and briefs. Use for "воронка", "funnel analysis", "drop-off", "where are users dropping", "что трекать", "event schema", "tracking plan", "cohort analysis", "трекинг событий".
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
Picks UI patterns that address the mechanism of a solution hypothesis — for wireframing in /sketch. Use when sketching a solution, choosing between interface approaches, or when the user says "какой паттерн использовать", "what component to use", "UI pattern", "how should this screen work", "нарисуй экраны".
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
Creates detailed user personas from research data combining demographics, psychographics, behavioral patterns, goals, and pain points. Use when user needs to build personas, segment users, or says "user persona", "create persona", "user segments", "who is our user", "target audience profile", "персона пользователя"…
lenar-amirov/product-pipeline-public
Skill Claude CodeCodex
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"…