qa-aman
- 215 skills
- 0 followers
- 26 repo stars
- 6 days ago last updated
- ▌ Karpathy Guidelines · qa-amanBehavioral guardrails against the six most common LLM coding failure modes: unstated assumptions, overbuilding, changes beyond the ask, no success condition, claiming done without output, and sprawling non-atomic changes. Use when writing, editing, reviewing or refactoring code, when the user says 'keep it simple', 'surgical change', 'don't over-engineer', 'minimal diff' or 'verify before saying done', or when a change keeps growing beyond the ask. For a full code review, see code-review.
- ▌ Competitor Analyst · qa-aman bundleAnalyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md. For a lightweight competitor summary in the knowledge base, see brand-context. For positioning against them, see positioning-doc. For a product or feature-level comparison outside the marketing knowledge base, see competitive-analysis.
- ▌ Campaign Brief · qa-aman bundlePlan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for [product], demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/. For a full quarterly strategy rather than one campaign, see marketing-plan scope in positioning-doc and kpi-review. For the content schedule inside the campaign, see social-calendar. For the post-campaign review, see retro.
- ▌ Meeting To Spec Update · qa-amanUpdate a product spec from a meeting transcript — extract decisions, open questions, spec changes, and flowchart updates. Use this skill when: - A meeting discussed changes to a product spec and you need to update the local .md + wiki page - The user shares a meeting URL or transcript ID and says "update the spec" - The user says "what needs to change in the spec from this meeting" - After processing a meeting, when decisions affect a spec's content (not just action items) Trigger phrases: "update spec from meeting", "what changed in the spec", "meeting to spec", "sync meeting decisions to spec", "add meeting decisions to spec"
- ▌ Figma Copy Rewriter · qa-aman bundleRewrite UI copy directly on Figma files to be simpler, jargon-free, and terminologically consistent. Trigger when: user says "rewrite copy", "simplify copy", "fix the text", "copy audit", "UX copy review", "clean up the wording", shares a Figma URL and mentions copy/text/wording, or asks to make text simpler/clearer/more consistent on a Figma file.
- ▌ Draft Email · qa-amanDraft professional emails (MoM, status updates, decisions, stakeholder communication) and save as a draft in your email provider. Use this skill after a meeting, decision, spec update, or any event that needs email communication. Trigger phrases: "send MoM email", "draft meeting minutes email", "MoM email for [meeting]", "create MoM draft", "email the meeting notes", "draft MoM", "draft email", "send update email", "draft email for [topic]". Reads context from meetings, specs, tickets, and conversation. Looks up attendee emails from a local team directory, formats as HTML email, and pushes to the email provider as a draft (never sends).
- ▌ Retro · qa-aman bundleCapture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief. For turning a sprint team's retro notes into action items, see retro-synthesizer.
- ▌ Confluence To Md · qa-aman bundleConvert Confluence pages to clean GitHub-Flavored Markdown files. Use this skill whenever the user wants to pull a Confluence page into the local repo, convert Confluence content to markdown, download a spec from Confluence, or batch-convert multiple pages. Also triggers on Confluence URLs, page IDs, or phrases like "pull this page", "download this spec", "confluence to md". Use this even if the user just pastes a Confluence URL and says something vague like "get this" or "convert this".
- ▌ Md To Confluence · qa-aman bundlePush markdown files to Confluence - update existing pages or create new ones under a parent page. Use this skill whenever the user wants to publish markdown to Confluence, update a Confluence page from a local .md file, create new Confluence pages, or batch-create pages. Also triggers on "push to confluence", "update confluence page", "create confluence page", "publish to confluence", "sync to confluence", or any mention of uploading/pushing markdown content to Confluence. Use this even when the user says "put this on confluence" or "make a confluence page for this".
- ▌ Ppt Maker · qa-aman bundleBuild branded PowerPoint decks (.pptx) for pitches, internal updates, sales decks, customer QBRs, board updates, conference talks using the Pyramid Principle and SCQA framework (Barbara Minto, The Minto Pyramid Principle). Every deck starts with the answer - conclusion on slide 2, evidence after. Slide titles are conclusions, not topics. Use when the user asks for a deck, presentation, slides, pitch deck, sales deck, board deck, QBR, "make slides for X", or "build a presentation". Uses templates/ for brand assets. Generates structured slide content with speaker notes. For the narrative content of the deck, see thought-leadership-writer or campaign-brief. For a case study slide, see case-study-writer. For slide content only, without a .pptx file, see presentation-builder.
- ▌ Pm Weekly Update · qa-amanGenerate weekly or monthly status updates from local PM data. Use this skill when: - It's end of week and you need a status update for leadership or stakeholders - You need a monthly executive summary - You want to draft an email update using data from meetings, tracker tickets, and decisions - The user says "weekly update", "status report", "what happened this week?", "weekly summary" - The user says "Friday update", "send status email", "EOW update" Pulls from work logs, meetings, ticket tracker, and decisions — no manual input needed.
- ▌ Spec To UX Tasks · qa-amanExtract UX tasks from a product spec and save as ux-tasks.md in the same spec folder. Use this skill when: - The user wants to generate UX work items from a spec - The user says "UX tasks", "what does UX need to do", "extract UX work", "UX deliverables" - The user wants to hand off a spec to the UX/design team - The user asks "what screens need designing" or "what UX decisions are open"
- ▌ Presentation Builder · qa-amanTransform ideas, outlines, or documents into structured slide content with clear titles, bullet points, and speaker notes. Adapts to presentation type (pitch decks, business reviews, technical workshops, educational talks). Use when user says "create slides", "build a deck", "pitch deck", "presentation structure", "talk structure", "keynote", "slide deck", "conference talk", or needs slide content for any format. Also trigger when user has content they want to present to an audience - even if they don't explicitly say "presentation" or "slides". To produce a branded .pptx file, see ppt-maker.
- ▌ Brand Namer · qa-aman bundleGenerate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.
- ▌ Experiment Design 2 · qa-amanDesign product experiments to test hypotheses. Use when the user says "run an experiment", "A/B test this", "build-measure-learn", "validate this assumption", "test this hypothesis", "we don't know if this will work", "minimum viable test", "lean experiment", or wants to reduce risk before fully building a feature - even if they don't explicitly say "experiment". For sample sizes, power calculations and significance testing, use ab-test-design instead.
- ▌ Retro Synthesizer 2 · qa-amanSynthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions For a marketing campaign or launch retro that writes learnings to knowledge/, see retro.
- ▌ Competitive Analysis 2 · qa-amanConduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis". For marketing positioning work that writes to knowledge/markets/competitors.md, see competitor-analyst.
- ▌ Ab Test Design · qa-amanDesign statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.
- ▌ Better Way · qa-amanChallenge the user's stated approach and propose a clearly better one before doing the work. Use when the user types /better-way, "better?", "is there a better approach", "any better idea", "what would you do instead", "is this the best way", or shares their own plan and asks whether it is the right one. Works in any project. For a full written decision document with options and scoring, see decision-matrix.
- ▌ Teach Me · qa-amanTeach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.
- ▌
- ▌
- ▌ Jira Ticket Creator 2 · qa-amanCreate Jira tickets from meeting notes, user stories, or quick lists. Use this skill when: - User says "create tickets", "make Jira tickets from", "push to Jira" - User has meeting action items to convert to tickets - User has user stories from a spec to push to the backlog - User wants to batch-create tasks, stories, or bugs
- ▌ Write Prd 2 · qa-amanWrite a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".
- ▌ Okr Writer 2 · qa-amanWrite OKRs (Objectives and Key Results). Use when the user says "write OKRs", "help me set goals", "create objectives and key results", "quarterly goals", "team OKRs", "I need to define success for this quarter", "Doerr method", or wants to translate a strategic direction into measurable targets - even if they don't explicitly say "OKRs".
- ▌ Team Brief 2 · qa-amanWrite an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".
- ▌ Feature Spec 3 · qa-amanWrite a concise feature spec for engineering handoff. Use when the user says "write a spec", "feature spec", "one-pager for eng", "spec this out", "write up this feature", "I need to hand this off to engineering", "shape this up", or wants a concise technical brief - even if they don't say "feature spec".
- ▌ Pilot Debrief 2 · qa-amanSynthesize pilot observations into structured debrief reports and spec updates. Use this skill when: - A pilot has completed and you have observation notes, tickets, or feedback transcripts - You need to turn messy pilot data into actionable spec changes - You want to generate edge case user stories from field observations - You need negative acceptance criteria from pilot bugs - You want a structured debrief report for stakeholder communication
- ▌ Risk Register 2 · qa-amanMaintain a centralized living risk register across projects. Use this skill when: - You need to create or update a risk register for a project or feature - You want to consolidate risks from individual specs into one register - You need to review and update risk status, mitigations, and owners - You want a cross-project risk view
- ▌ Spec Reviewer 2 · qa-amanQuality gate for product specifications before stakeholder review. Use this skill when: - A spec draft is ready and you want to validate it before sending to Engineering, Design, and QA - You want to check a spec against your template's completeness rules - You need to catch vague language, missing sections, or gaps before review - You want a pass/fail scorecard with specific fix suggestions
- ▌ Epic Breakdown 2 · qa-aman bundleDecompose large epics into sprint-ready sub-epics using 9 splitting patterns. Use this skill when: - A spec is approved and you need to break a large feature into estimable work items for engineering - You want to split an epic that is too large for a single sprint - You need sized sub-epics with story point estimates for sprint planning - You are preparing for engineering handoff and need to identify work packages
- ▌ Prioritization 2 · qa-amanPrioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".
- ▌ Youtube Transcript 2 · qa-aman bundleFetch transcripts from YouTube videos. Use when user says "get transcript", "fetch transcript", "YouTube transcript", "pull captions", "what does this video say", or pastes a YouTube URL and wants the text content extracted. Also use when user wants to research or summarize a YouTube video.
- ▌ Persona Updater 2 · qa-amanUpdate user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data
- ▌ Product Thinking 2 · qa-aman bundleRun structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief
- ▌ Retention Design 2 · qa-amanDesign retention and engagement features using the Hook Model. Use when the user says "improve retention", "reduce churn", "make it habit-forming", "engagement design", "hook model", "trigger action reward", "users aren't coming back", "increase DAU/MAU", or wants to design features that bring users back repeatedly - even if they don't explicitly say "Hook Model".
- ▌ 11 Star Framework 2 · qa-amanRate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".
- ▌ Outcome Vs Output 2 · qa-amanAudit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".
- ▌ Product Discovery 2 · qa-amanRun product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".
- ▌ Compliance Auditor 2 · qa-amanAudit feature specs against India's Digital Personal Data Protection (DPDP) Act. Use this skill when: - Writing or reviewing any feature that handles user data (especially children's data) - Auditing a spec's Personal Information section for completeness - Checking a feature against DPDP Act 2023 requirements - Preparing compliance documentation before engineering review - Verifying masking, retention, and consent policies are defined for all PII
- ▌ Product Market Fit 2 · qa-amanAssess and improve product-market fit. Use when the user says "product-market fit", "PMF", "do we have PMF", "why aren't users retaining", "we're not growing", "users aren't sticking", "PMF pyramid", "find our target customer", "are we building for the right person", or wants to diagnose why a product isn't growing or retaining - even if they don't explicitly say "product-market fit".
- ▌ Stakeholder Update 2 · qa-amanGenerate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report
- ▌ Write User Stories 2 · qa-amanWrite user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".
- ▌ Release Notes Writer 2 · qa-amanGenerate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets
- ▌ Go To Market Checklist 2 · qa-amanGenerate a pre-launch readiness checklist for feature releases. Use this skill when: - A feature is nearing completion and you need a launch readiness checklist - You want to ensure all pre-launch items are covered (docs, training, support, rollback) - You are planning a phased rollout and need a structured go-to-market plan
- ▌ Discovery Interview Prep 2 · qa-amanGenerate user research interview scripts using Mom Test principles. Use this skill when: - You are preparing for user interviews or pilot observation sessions - You need a question bank organized by behavior, context, pain points, and workflow - You want interview guides that avoid leading questions and hypotheticals - You need per-persona interview guides - You are preparing for field visits or pilot debriefs
- ▌ Opportunity Solution Tree 2 · qa-amanBuild Opportunity Solution Trees using Teresa Torres' framework for structured product discovery. Use this skill when: - You need to map a desired outcome to opportunities, solutions, and experiments - You want to decide WHAT to build next based on user research and discovery data - You have workshop findings, pilot feedback, or user research to structure into actionable options - You need a visual tree diagram showing the path from outcome to testable experiments
- ▌ Feature Spec 2 · qa-amanWrite a concise feature spec for engineering handoff. Use when the user says "write a spec", "feature spec", "one-pager for eng", "spec this out", "write up this feature", "I need to hand this off to engineering", "shape this up", or wants a concise technical brief - even if they don't say "feature spec".
- ▌ Mom · qa-amanTurn a file of raw meeting notes, minutes, or a transcript into a ready-to-send Minutes of Meeting (MoM) written in Axios Smart Brevity style. Use this skill whenever the user wants to write, produce, format, share, or send meeting minutes or a MoM from a notes file, even if they don't say "Smart Brevity". Trigger on phrases like "send the MoM", "create minutes of meeting", "write up the MoM", "turn these meeting notes into minutes", "share the meeting summary", "MoM for this meeting", "minutes from the sync/standup/review", or when the user points at a meeting notes file and asks for minutes to circulate. Do NOT trigger for daily standup digests (use standup-summary) or for drafting an email (use email-drafter) unless the user explicitly wants meeting minutes.
- ▌ Pr Faq · qa-aman bundleRun Amazon's Working Backwards PR/FAQ process as a guided interview, then produce a full PR/FAQ document plus an explicit Go / No-Go / Not-Yet build decision. Use this skill when the user says "PR FAQ", "PRFAQ", "press release FAQ", "working backwards", "should we build this", "is this feature worth building", "help me decide whether to build X", "pressure-test this idea", "write a PR/FAQ for [feature]", or wants to validate a feature idea before committing engineering time. Also trigger when the user has a feature idea and wants a customer-first go/no-go decision, even if they never say "PR/FAQ".
- ▌ Work Log · qa-aman bundleBuild the daily work log for this project from its Claude Code JSONL session transcripts. Reads every transcript, works out which days had activity, checks which of those days already have a log file in .local/log/, then writes today's log and backfills any missing day. Use when Aman says "/work-log", "work log", "log my work", "create the work log", "what did I do today", "what did I work on on <date>", "backfill my work logs", or wants a record of the work done in this repo on a given day. Project-scoped: only this repo's transcripts, only this repo's .local/log folder.
- ▌ Flowchart · qa-amanGenerate Mermaid flowchart diagrams from any input source. Use this skill when: - User wants to create flow diagrams, process flows, or decision trees - User provides a ticket, spec, or verbal description to visualize - User says "draw a flowchart", "create a diagram", "visualize this flow"
- ▌ Write Prd · qa-aman bundleWrite a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".
- ▌ Okr Writer · qa-amanWrite OKRs (Objectives and Key Results). Use when the user says "write OKRs", "help me set goals", "create objectives and key results", "quarterly goals", "team OKRs", "I need to define success for this quarter", "Doerr method", or wants to translate a strategic direction into measurable targets - even if they don't explicitly say "OKRs".
- ▌ Team Brief · qa-amanWrite an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".
- ▌ Ppt Builder · qa-aman bundleGenerate dark-themed, professional PowerPoint (.pptx) files using python-pptx. Invoke this skill whenever the user says "create a PPT", "build slides", "make a presentation", "generate a deck", or wants to turn a session plan, outline, content doc, or conversation into a slide deck. Also trigger when the user says things like "turn this into slides", "I need slides for this", or "make a deck for this session". The output is always a .pptx file using the design system defined in this skill. Do not write ad-hoc python-pptx code — always use this skill and the bundled script as the foundation.
- ▌ PPTX Editor · qa-aman bundleEdit, update, and add slides to PowerPoint (.pptx) files using python-pptx. Use this skill whenever the user wants to modify a presentation - adding slides, editing text, changing styling, reordering slides, inserting links, or fixing design consistency. Trigger on any mention of "slide", "presentation", "PowerPoint", "pptx", "deck", "add a slide", "update the slide", "fix the slides", "last slide", "thank you slide", or any request involving .pptx files - even if the user just references a .pptx path without explicitly saying "edit".
- ▌ UX Designer · qa-aman bundleDesign and review UI/UX, and deliver it as a clickable self-contained HTML mockup (default) or as a Figma file, so it can be judged before any development starts. Use whenever the user wants to design a screen, flow, page, dashboard, form, onboarding, empty state, or app, wants to see what a feature would look like, or wants existing UI critiqued or improved. Trigger on "design this screen", "what should this look like", "make a mockup", "wireframe this", "build a prototype of", "UI for this feature", "design the UX", "improve this screen", "review this UI", "why does this page feel confusing", "make this look better", "audit this interface", "turn this PRD into screens", and on any request to visualise a feature before engineering builds it. Also use when someone pastes a URL, screenshot, or component file and asks what is wrong with it, or when a spec is written and the natural next question is "how does it look". Prefer this skill over hand-rolling UI, and use it even when the user does not say "UX".
- ▌ Feature Spec · qa-amanWrite a concise feature spec (one-pager) for engineering handoff. Use when user says "write a spec", "one-pager", "feature spec", "spec this out", "spec for [feature name]", or wants a structured feature brief grounded in product context and user research.
- ▌ Email Drafter · qa-amanDraft professional emails using Barbara Minto's Pyramid Principle (SCQA, BLUF, MECE) and HBR Guide to Better Business Writing principles (clarity, brevity, reader-first framing). Use this skill whenever the user wants to write, draft, compose, or rewrite a work email - executive updates, decision requests, recommendations, proposals, cross-team asks, replies, follow-ups, or client updates. Trigger on phrases like "draft an email", "write an email to", "email my boss/team/client", "follow up with", "send an update", "reply to this thread", "compose a message", "I need to email", or whenever an email-shaped output is needed - even if the user does not say "email" explicitly (e.g., "tell my VP we're slipping the launch", "let the client know about the delay"). Also trigger when the user pastes an email thread and asks for a response.
- ▌ Pilot Debrief · qa-amanSynthesize pilot observations into structured debrief reports and spec updates. Use this skill when: - A pilot has completed and you have observation notes, tickets, or feedback transcripts - You need to turn messy pilot data into actionable spec changes - You want to generate edge case user stories from field observations - You need negative acceptance criteria from pilot bugs - You want a structured debrief report for stakeholder communication
- ▌ Risk Register · qa-amanMaintain a centralized living risk register across projects. Use this skill when: - You need to create or update a risk register for a project or feature - You want to consolidate risks from individual specs into one register - You need to review and update risk status, mitigations, and owners - You want a cross-project risk view
- ▌ Spec Reviewer · qa-amanQuality gate for product specifications before stakeholder review. Use this skill when: - A spec draft is ready and you want to validate it before sending to Engineering, Design, and QA - You want to check a spec against your template's completeness rules - You need to catch vague language, missing sections, or gaps before review - You want a pass/fail scorecard with specific fix suggestions
- ▌ Epic Breakdown · qa-aman bundleDecompose large epics into sprint-ready sub-epics using 9 splitting patterns. Use this skill when: - A spec is approved and you need to break a large feature into estimable work items for engineering - You want to split an epic that is too large for a single sprint - You need sized sub-epics with story point estimates for sprint planning - You are preparing for engineering handoff and need to identify work packages
- ▌ Prioritization · qa-amanPrioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".
- ▌ Persona Updater · qa-amanUpdate user personas from new feedback, pilot data, or research. Use this skill when: - New pilot data or feedback reveals changed user behaviors or pain points - Annual persona review is due (1-2x per year) - New user segments are discovered that need persona documentation - Existing personas need validation against recent data
- ▌ Session Debrief · qa-amanProcess a completed NextLeap workshop session from a Granola link into (1) a session summary file under .local/session-transcripts/may-2026/ and (2) appended Q&A entries in 02-presentation/q&a.md. Trigger whenever the user says "session completed", "session done", "process this Granola session", "debrief this session", "new workshop session", or pastes a Granola URL alongside a request to update the transcripts folder and q&a doc. Also trigger when the user references the q&a.md file or session-transcripts folder in a "just-finished-the-class" context.
- ▌ Standup Summary · qa-amanSummarize daily team standup notes into a structured markdown digest covering team progress, blockers, decisions, and action items. Use this skill whenever the user wants to process, summarize, condense, or recap daily standup notes, scrum notes, or daily sync notes, even if they don't explicitly say "standup". Trigger on phrases like "summarize the standup", "recap today's standup", "what happened in standup", "digest this standup", "standup summary for [date]", "turn these standup notes into a summary", or when the user points at a `daily-standup-*.md` file and wants it processed. Also trigger when the user wants to surface blockers, decisions, or owner-tagged action items from raw standup notes.
- ▌ Product Thinking · qa-aman bundleRun structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief
- ▌ Retention Design · qa-amanDesign retention and engagement features using the Hook Model. Use when the user says "improve retention", "reduce churn", "make it habit-forming", "engagement design", "hook model", "trigger action reward", "users aren't coming back", "increase DAU/MAU", or wants to design features that bring users back repeatedly - even if they don't explicitly say "Hook Model".
- ▌ Technical Review · qa-amanReview a feature spec for technical readiness before engineering walkthrough. Use when the user says "review this spec", "technical review", "is this spec ready for eng", "prepare for eng walkthrough", "check my spec", "what will engineers ask", "validate this spec", or wants to ensure a feature spec covers all technical dimensions before presenting to engineering. Also trigger when a spec has been written and the user mentions "walkthrough", "handoff", or "ready for review".
- ▌ 11 Star Framework · qa-amanRate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".
- ▌ Outcome Vs Output · qa-amanAudit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".
- ▌ Product Discovery · qa-amanRun product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".
- ▌ Retro Synthesizer · qa-amanSynthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions
- ▌ Compliance Auditor · qa-amanAudit feature specs against India's Digital Personal Data Protection (DPDP) Act. Use this skill when: - Writing or reviewing any feature that handles user data (especially children's data) - Auditing a spec's Personal Information section for completeness - Checking a feature against DPDP Act 2023 requirements - Preparing compliance documentation before engineering review - Verifying masking, retention, and consent policies are defined for all PII
- ▌ Product Market Fit · qa-amanAssess and improve product-market fit. Use when the user says "product-market fit", "PMF", "do we have PMF", "why aren't users retaining", "we're not growing", "users aren't sticking", "PMF pyramid", "find our target customer", "are we building for the right person", or wants to diagnose why a product isn't growing or retaining - even if they don't explicitly say "product-market fit".
- ▌ Stakeholder Update · qa-amanGenerate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report
- ▌ Write User Stories · qa-amanWrite user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".
- ▌ Youtube Transcript · qa-aman bundleFetch transcripts from YouTube videos. Use when user says "get transcript", "fetch transcript", "YouTube transcript", "pull captions", "what does this video say", or pastes a YouTube URL and wants the text content extracted. Also use when user wants to research or summarize a YouTube video.
- ▌ Launch Announcement · qa-aman bundleGenerate a complete feature launch kit (announcement blurb, customer email, in-app banner copy, social post) grounded in project repo files, using a three-layer framework stack - April Dunford positioning for grounding, StoryBrand SB7 for narrative structure, and the SUCCESs checklist for quality scoring. Use whenever the user mentions a launch announcement, launch kit, launch copy, launch messaging, GTM copy, release announcement, "announce [feature]", "marketing copy for [feature]", customer email for a launch, in-app banner, press release for a feature, blog announcement, changelog copy, "write the email to customers about [feature]", or wants any customer-facing copy for an upcoming or shipped feature - even if they never say the word "launch". Also use when a marketing teammate asks to "write copy" for a feature that exists in 08-product-features/ or 09-release-notes/.
- ▌ Pre Build Interview · qa-aman bundleRun pre-build user interviews to validate whether a planned feature actually solves a real problem before engineering invests. Use when the user says "validate this feature", "should we build this", "interview users about [feature]", "test this feature idea", "pre-build validation", "is this feature worth building", "talk to users first", or has a feature idea and wants to pressure-test it with real users before writing a PRD or kicking off engineering. Also trigger when the user wants to avoid building something users will not adopt, when they say "what would users actually think of this", or when they have a hypothesis and need a structured interview plan. Combines Mom Test question discipline, Lean Customer Development hypothesis structure, JTBD Forces of Progress, and Opportunity Solution Tree synthesis into one workflow that ends with a clear build / iterate / kill recommendation.
- ▌ Competitive Analysis · qa-amanConduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis".
- ▌ Release Notes Writer · qa-amanGenerate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets
- ▌ Competitor Page Audit · qa-aman bundleAudit your product page against a competitor's page and produce a visual scorecard where every gap comes with an exact, reasoned fix. Use whenever the user wants to compare their page to a competitor, says "teardown this page vs theirs", "why is my page losing to X", "audit my landing page against [competitor]", "compare my product page to the competition", "where is my page worse than theirs", or gets vague page-improvement suggestions from another tool and wants specifics. Also trigger when the user has two page URLs or screenshots and wants to know what to change, what's missing, or where users get stuck - even if they don't say "audit".
- ▌ Go To Market Checklist · qa-amanGenerate a pre-launch readiness checklist for feature releases. Use this skill when: - A feature is nearing completion and you need a launch readiness checklist - You want to ensure all pre-launch items are covered (docs, training, support, rollback) - You are planning a phased rollout and need a structured go-to-market plan
- ▌ Discovery Interview Prep · qa-amanGenerate user research interview scripts using Mom Test principles. Use this skill when: - You are preparing for user interviews or pilot observation sessions - You need a question bank organized by behavior, context, pain points, and workflow - You want interview guides that avoid leading questions and hypotheticals - You need per-persona interview guides - You are preparing for field visits or pilot debriefs
- ▌ Ticket Category Analysis · qa-aman bundleCategorize free-text support tickets into a 3-tier taxonomy and produce a month-on-month management report, an interactive dashboard, and a shareable PowerPoint. Use this skill whenever someone has a batch of tickets, requests, incidents, or cases and wants to know what categories they fall into, how the volumes are trending month on month, or what management should act on. Trigger on ServiceNow, Jira Service Management, Freshservice, Zendesk, or any helpdesk export; on phrases like "categorize these tickets", "tag these requests", "what are people raising", "monthly ticket report", "ticket volume trends", "which category is growing", "what should we automate", "service desk analysis", "bucket these descriptions", "how many tickets per category"; and whenever someone describes manually reading ticket descriptions to sort them into buckets, which is the exact pain this removes. Also use it when there is no ticket data yet and a realistic sample plus a working report is needed to show a stakeholder what the out
- ▌ Opportunity Solution Tree · qa-amanBuild Opportunity Solution Trees using Teresa Torres' framework for structured product discovery. Use this skill when: - You need to map a desired outcome to opportunities, solutions, and experiments - You want to decide WHAT to build next based on user research and discovery data - You have workshop findings, pilot feedback, or user research to structure into actionable options - You need a visual tree diagram showing the path from outcome to testable experiments
- ▌ Code Improvement Frameworks · qa-aman bundleNamed, first-party frameworks for judging and improving code quality - Martin Fowler's refactoring catalog and code smells, Google's engineering-practices code review standard, and the official React, Next.js and TypeScript guidance. Use this skill whenever you are reviewing, improving, refactoring, polishing, or critiquing code, or deciding whether a piece of code is good enough: it turns a vague 'this feels messy' into a named smell, a named refactoring, and a citable source. Load it before writing any code-quality finding, including inline review comments, PR reviews, refactor plans, and improvement reports, and even when the request sounds like a quick once-over. Preload it into review subagents through the `skills:` frontmatter field rather than restating its content in the agent body.
- ▌ Sync Skills · qa-amanFetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when user says "sync skills", "fetch skills", "import skills from projects", or wants to pull skills from their local projects into this public repo.
- ▌ Create Skill · qa-amanCreate or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill", "new skill", "write a skill", "update a skill", "skill standard", or any time a new SKILL.md file needs to be created. Also use when reviewing existing skills for standards compliance.
- ▌ QA Metrics · qa-amanBuild QA quality dashboards, calculate defect metrics, analyze escape rates, and produce quality trend reports. Use this skill whenever a QA lead or manager needs to measure and communicate quality outcomes. Trigger on phrases like "quality metrics", "defect density", "escape rate", "bug trends", "quality dashboard", "sprint quality report", "test coverage metrics", "QA KPIs", "how is quality trending", "defect leakage", "production bugs this quarter", "mean time to detect", "quality scorecard", or any request to quantify, visualize, or report on the quality of a product or testing process. Also trigger when a manager asks "how is QA performing?" or an engineering lead asks "what does our defect data tell us?".
- ▌ QA Release · qa-amanManage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".
- ▌ Runbook · qa-amanWrite an operational runbook. Use when the user says "write a runbook", "on-call documentation", "how to operate this service", "alert runbook", "troubleshooting guide for ops", "what to do when this alert fires", "operational procedures", or needs to document how to run, troubleshoot, or respond to a service - even if they don't explicitly say "runbook".
- ▌ Debug · qa-amanDebug a bug or unexpected behavior systematically. Use when the user says "there's a bug", "this isn't working", "I'm getting an error", "help me debug", "why is this failing", "unexpected behavior", "test is failing", "something is broken", or describes behavior that doesn't match expectations - even if they don't say "debug".
- ▌ QA Strategy · qa-amanCreate QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"
- ▌ QA Execution · qa-amanRun and document QA test execution cycles - smoke tests, regression suites, exploratory testing sessions, and release readiness checklists. Use this skill whenever a QA engineer needs to structure or report on active testing work. Trigger on phrases like "run smoke tests", "start a regression cycle", "exploratory testing session", "test this build", "release checklist", "is this build stable", "log test results", "what passed and what failed", "document my testing", "create a test run report", or any request to execute and record test outcomes. Also trigger when someone says "we need to test before release" or "can you help me track what I've tested".
- ▌ Diagram Generator · qa-amanGenerate diagrams of any kind from a description, ticket, spec, or file. Outputs Mermaid syntax (renders natively in GitHub, Notion, Confluence, Obsidian, Slack with apps) plus an optional single-file HTML preview that renders the diagram in the browser. Use this skill when the user says: - "draw a flowchart", "create a diagram", "visualize this flow" - "sequence diagram", "state diagram", "ER diagram", "class diagram" - "user journey", "mindmap", "timeline", "gantt", "org chart" - "sankey", "quadrant chart", "git graph" - or pastes a ticket / spec / description and asks for a visual Picks the right Mermaid diagram type for the input, asks if ambiguous, then emits clean syntax + an optional preview file.
- ▌ UX Audit · qa-amanAudit a user flow for friction and drop-off points. Use when the user says "UX audit", "audit this flow", "where are users dropping off", "why isn't this converting", "review the onboarding", "usability audit", "what's causing friction", "user journey review", or wants to identify why users struggle with a flow - even if they don't explicitly say "UX audit".