Claude Skills by lenar-amirov

Structures vague opportunities and unclear briefs into actionable

Conducts structured heuristic evaluation of design decisions and

Synthesises user signals from multiple research sources into a

Detailed instructions for each pipeline step (0-18). Read this when PM calls a specific pipeline command like /analyze-cjm, /validate-problems, etc.

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".

Step 0 of the PM Pipeline. Guides the PM through an alignment checklist before any work begins.

Generates the strategic story connecting your roadmap to company

Creates system design documents covering architecture, technical dependencies, data flows, APIs, and infrastructure. Use when user needs to document technical architecture, identify dependencies, or says "system design", "architecture document", "technical dependencies", "design doc", "системный дизайн", "архитектурный документ".

Creates detailed technical specification documents that translate requirements into implementation blueprints for development teams. Use when user needs a tech spec, component documentation, or says "technical spec", "tech spec", "implementation spec", "specification document", "технический документ", "спецификация".

Provides UI patterns and component architecture guidance for designing consistent interfaces including design tokens and component documentation. Use when user needs UI patterns for wireframes, component design guidance, or says "UI pattern", "what component to use", "interface patterns", "wireframe pattern", "UI components", "какой паттерн использовать".

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", "персона пользователя", "создай персону".

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", "пользовательские истории".

Adversarial gate rehearsal — a hostile stakeholder attacks the presentation against the hypothesis registry before the real gate does. Use when the PM says "завтра защита", "порепетируем гейт", "challenge my deck", "attack this presentation", "прогони как злой стейкхолдер", or before any Gate 1 / Gate 2 review.

Facilitated partner-led thinking session for problems that are NOT initiatives yet — strategy questions, org decisions, "should we enter X" — where there is no metric gap to pipeline. The PM leads, Claude structures and executes. Use for "давай подумаем стратегически", "помоги продумать сложный вопрос", "стоит ли нам…", "как подойти к реорганизации", "think this through with me", "у меня нет метрики, но есть проблема". When the problem IS a metric gap — that's /hypotheses, not this.

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", "как проверим решение", "критерии успеха теста".

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 "мне принесли дек", "вот данные/выгрузка", "прочитай этот PDF", "ingest this", "here's a deck from the analyst".

Turns raw user-interview notes into coded patterns and registry verdicts — the method behind validation 6c and any qualitative debrief. Use for "вот заметки с интервью", "interview notes", "разбери интервью", "что сказали пользователи на интервью", "проанализируй звонки с клиентами".

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.

Closes the loop after launch — compares actual metric movement against the target set in Frame, issues production verdicts to hypotheses, and banks reusable facts into the PM's knowledge base. Use when the PM says "post-launch review", "прошло N месяцев после запуска", "метрика сдвинулась?", "подведём итоги инициативы", or when a post_launch_review dependency comes due.

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".

Assumption mapping, ICE/SIF scoring and business viability check for solution hypotheses — the scoring engine of /solutions (step 7). Use for "какое решение выбрать", "ICE scoring", "assumption map", "prioritize solutions", "оцени решения", "риски этого решения".

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", "трекинг событий".

Designs user tests in two modes — quick 15-minute concept test on wireframes (3-5 users) or a full usability study (methodology, participants, tasks, severity coding). Use for "concept test", "проверить концепт на пользователях", "usability test", "юзабилити-тест", "user testing", "test the prototype", "план UX-исследования", "sample size for user test".