Use this file to match user requests to a skill before opening SKILL.md. Purposes mirror each skill’s description in frontmatter.
Three sources land in the same tree:
- skill-factory — imported into this repo via
./pull-and-sync-skills.sh/./sync-skill-factory.sh - Product management pack —
pmprompt/claude-plugin-product-management(integrity: repo-rootskills-lock.json; taxonomy and overlaps: .agents/skills/skill-foundry/agents/catalog-product-management.yaml) - Native skills — authored and maintained directly in this repository
| Skill | Category | Purpose |
|---|---|---|
| traductor-bilingue | tools | Translates technical text between English and Spanish preserving tone and format. Keeps technical terms in English when common in Spanish dev teams (deploy, pull request, pipeline, staging). Use when translating technical documentation, code comments, or team communication. |
| test-desiderata | testing | Analyze and improve test code quality using Kent Beck's Test Desiderata framework. Use when analyzing test files, reviewing test code, identifying test quality issues, suggesting test improvements, or when asked to evaluate tests against best practices. Applies to unit tests, integration tests, and any automated test code. |
| tdd | testing | Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike. |
| nullables | testing | Writes tests without mocks using Nullables. Use when writing tests, especially testing code with external I/O (HTTP, files, databases, clocks, random numbers), designing infrastructure wrappers or replacing mocking libraries. |
| mutation-testing | testing | Finds weak or missing tests by analyzing if code changes would be caught. Use when verifying test effectiveness, strengthening test suites, or validating TDD workflows. |
| bdd-with-approvals | testing | Write executable BDD specifications as approval-test fixtures in domain language. Use when doing BDD, writing Given/When/Then specs, creating human-scannable test fixtures, or turning event model slices into executable tests. Pairs with event-modeling and approval-tests skills. Not for unit test mechanics or mock setup. |
| approval-tests | testing | Writes approval tests (snapshot/golden master testing) for Python, JavaScript/TypeScript, or Java. Use when verifying complex output, characterization testing legacy code, testing combinations, or working with .approved/.received files. |
| thinkies | practices | Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions. |
| thin-wrappers | practices | Encapsulates infrastructure SDKs behind minimal domain-aligned interfaces. Use when accessing any external infrastructure to keep SDK usage contained, testing simple, and changes easy. |
| story-splitting | practices | Detects stories that are too big and applies splitting heuristics. Identifies linguistic red flags (and, or, manage, handle, including) and suggests concrete splitting strategies. Use when breaking down requirements or splitting large work. |
| small-safe-steps | practices | Small Safe Steps (S3): breaks work into 1-3h increments with zero downtime. Use when asking "how do I implement/migrate/refactor", "what steps to do X", "plan safe migration", or handling risky DB/API changes. Applies expand-contract pattern for migrations, refactorings, schema changes. |
| refinement-loop | practices | Iterative refinement through multiple passes. Use when the user asks to 'meditate on', 'distill', 'refine', or 'iterate on' something, or proactively when a problem benefits from multiple passes rather than a single attempt. |
| refactoring | practices | Structured refactoring process with prep, main refactoring, final evaluation, and summary phases. Use when asked to "refactor", "clean up code", "improve readability", or proactively when code gets too complex or messy. For XP simple-design refactoring with ROI prioritization use xp-simple-design-refactor; for safe large-scale refactoring use xp-mikado-method. |
| hamburger-method | practices | Slices features into vertical deliverable pieces using the Hamburger Method. Generates 4-5 implementation options per layer and composes minimal end-to-end slices. Use when slicing work, breaking down features into layers, or delivering incrementally. |
| complexity-review | practices | Reviews technical proposals against 30 complexity dimensions. Questions necessity of scale, consistency, and resilience. Use when proposing technologies (Kafka, microservices, event sourcing) or designing systems. Pushes for simplest viable approach. |
| code-simplifier | practices | Simplifies and refines code for clarity, readability, and maintainability. Reduces complexity without changing behavior. Use when simplifying, cleaning up, or reducing complexity in code. |
| writing-bash-scripts | developer-tools | Bash script style guide. Always use when writing bash scripts, shell scripts, or CLI bash tools. |
| using-uv | developer-tools | Python package and project management with UV. Use when creating Python scripts, initializing projects, or managing dependencies. |
| bun-toolkit | developer-tools | JS/TS/JSX toolkit with Bun awareness. Use when using Bun as a runtime, test runner, or package manager in JavaScript and TypeScript projects. |
| git-worktrees | developer-tools | Creates git worktrees for parallel development. Use when creating a git worktree, setting up multiple working directories, or working on features in parallel. |
| dockerfile-review | developer-tools | Reviews Dockerfiles for build performance, image size, and security issues. Use when optimizing, validating, or improving Dockerfiles. |
| modern-cli-design | design | Principles for scalable, modern command-line tools - object-command architecture (noun-verb), LLM-optimized help, JSON output, concurrency patterns, credential management. Use when building CLIs, designing command structures, or implementing terminal applications. |
| hexagonal-architecture | design | Applies hexagonal (ports & adapters) architecture. Use when designing application structure, separating domain from infrastructure, creating testable boundaries, or when user mentions ports, adapters, hexagonal, or clean architecture. |
| event-modeling | design | Design systems using Event Modeling with vertical slices (STATE_CHANGE, STATE_VIEW, AUTOMATION). Use when asked to "model a domain", "design event-driven system", "map commands and events", "create system slices", or doing domain-driven design from scratch or over existing code. Not for infrastructure event buses or message broker configuration. |
| collaborative-design | design | Designs software features collaboratively through visual scenarios and iterative refinement. Use when designing features, tools, UIs, workflows, or any system before implementation. |
| creating-process-files | ai | Creates process files - text as code instructions for reliable AI workflows. Use when creating new process files. |
| writing-statuslines | ai | Writes Claude Code status line scripts. Use when creating, customizing, or debugging statusline configurations. |
| creating-hooks | ai | Create and configure Claude Code hooks for lifecycle automation (pre/post tool use, session start, prompt submit, notifications). Use when asked to "add a hook", "auto-format on save", "block dangerous commands", "inject context on prompt", or "notify when done". Not for general shell scripting or CI/CD pipelines. |
| ai-patterns | ai | Reference patterns for augmented coding with AI. Use when discussing AI coding patterns, anti-patterns, obstacles, context management, steering AI, or looking up Lexler's patterns collection. |
| Skill | Category | Purpose |
|---|---|---|
| ab-test-designer | product-management | Design robust A/B test experiments. Use when testing a new feature, validating a hypothesis, or optimizing conversion rates. |
| design-sprint | product-management | Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days. The Design Sprint framework (created by Jake Knapp at Google Ventures) compresses months of work into one focused week. |
| feature-prioritization-assistant | product-management | Calculate RICE scores and prioritize features systematically. Use when building your product roadmap and need to make data-driven prioritization decisions. |
| growth-loops | product-management | Use when asked to "growth loops", "build a growth engine", "design a viral loop", "create a content loop", "move beyond paid acquisition", or "why isn't growth compounding". Helps design self-reinforcing growth systems where output becomes input. The Growth Loops framework (from Brian Balfour / Reforge and Elena Verna) shifts thinking from linear funnels to compounding loops. |
| hierarchy-of-engagement | product-management | Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework". Helps consumer products identify the actions and benefits that drive long-term retention. The Hierarchy of Engagement framework (created by Sarah Tavel at Benchmark) maps progression from core action to mounting loss. |
| hierarchy-of-marketplaces | product-management | Use when asked about "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", or "Sarah Tavel marketplaces". Helps founders and product leaders build defensible marketplace businesses by sequencing supply and demand. The Hierarchy of Marketplaces framework (created by Sarah Tavel / Benchmark) provides a progression from focused launch to market dominance. |
| hooked-model | product-management | Use when asked to "build habit-forming products", "Hooked model", "trigger action reward investment", "create sticky behavior loops", or "design habit loops". Helps design products that form unprompted user habits. The Hooked Model (created by Nir Eyal) explains how products create habits through Trigger, Action, Variable Reward, and Investment. |
| jobs-to-be-done | product-management | Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors". Helps discover unmet needs and the context behind purchasing decisions. The Jobs to be Done framework (created by Clayton Christensen and Bob Moesta) explains why customers hire and fire products. |
| monetizing-innovation | product-management | Use when asked about "pricing strategy", "willingness to pay", "value metric", "packaging tiers", "good better best pricing", "subscription vs usage pricing", or "price before product". Helps design products customers will pay for and choose pricing models that capture value. Based on Madhavan Ramanujam's Monetizing Innovation framework from Simon-Kucher. |
| okrs | product-management | Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls. |
| opportunity-solution-trees | product-management | Use when asked to "opportunity solution tree", "OST", "Teresa Torres", "map customer opportunities to outcomes", "structure discovery around opportunities", or "compare solutions for a customer need". Helps product teams connect outcomes to customer opportunities and test solutions with Opportunity Solution Trees (created by Teresa Torres). |
| pmf-survey | product-management | Use when asked to "PMF survey", "measure product-market fit", "40% rule", "Sean Ellis test", "Rahul Vohra method", or "how disappointed would you be". Helps quantify product-market fit and systematically improve it. The PMF Survey framework (created by Sean Ellis, popularized by Rahul Vohra at Superhuman) measures how disappointed users would be without your product and turns that data into a roadmap. |
| positioning-canvas | product-management | Use when asked to "position my product", "positioning canvas", "differentiate from competitors", "figure out our category", "repositioning", or "why customers should pick us". Helps define competitive alternatives, differentiated value, target customers, and market category. April Dunford's positioning framework from "Obviously Awesome" makes your product's value obvious to the right customers. |
| prd-writer | product-management | Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation. |
| product-led-growth | product-management | Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth". Helps design and optimize product-led growth motions where the product drives acquisition, activation, and monetization. Based on frameworks from Elena Verna and Hila Qu. |
| product-led-seo | product-management | Use when asked to "product-led SEO", "programmatic SEO", "build programmatic pages", "organic acquisition for product", "decide if SEO is worth it", or "optimize for AI search". Helps evaluate whether SEO fits your business model and how to approach it as a product, not just marketing. The Product-Led SEO framework (created by Eli Schwartz) treats SEO as building products for search users. |
| radical-candor | product-management | Use when asked to "radical candor", "give feedback that cares", "have a difficult conversation", "challenge directly", "manage performance issues", or "give praise that lands". Helps deliver direct feedback while showing you care. The Radical Candor framework (created by Kim Scott) teaches how to challenge directly while caring personally. |
| seven-powers | product-management | Use when asked to "7 Powers", "build a competitive moat", "analyze defensibility", "find sustainable advantage", "economic moats", or "Hamilton Helmer framework". Helps identify durable competitive advantages. The 7 Powers framework (created by Hamilton Helmer) reveals the economic structures that protect business value from competition. |
| shape-up | product-management | Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable scope, and collaborative shaping to ship meaningful work predictably. |
| stakeholder-update-generator | product-management | Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders. |
| strategic-narrative | product-management | Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change. |
| thinking-in-bets | product-management | Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions. |
| trustworthy-experiments | product-management | Use when asked to "run an A/B test", "design an experiment", "check statistical significance", "trust our results", "avoid false positives", or "experiment guardrails". Helps design, run, and interpret controlled experiments correctly. Based on Ronny Kohavi's framework from "Trustworthy Online Controlled Experiments". |
| user-feedback-synthesizer | product-management | Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis. |
| working-backwards | product-management | Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD". Helps define products by starting with the customer problem and desired outcome before building. The Working Backwards process (developed at Amazon) forces clarity on customer value before committing engineering resources. |
| Skill | Category | Purpose |
|---|---|---|
| fic-create-plan | workflow | Build a detailed, phase-based implementation plan from research or a task description. Use when the user asks for implementation planning, phased rollout, or a concrete execution plan. |
| fic-implement-plan | workflow | Execute an approved implementation plan phase by phase with verification. Use when the user asks to implement a plan file from thoughts/shared/plans. |
| fic-research | workflow | Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings. |
| fic-validate-plan | workflow | Validate that an implementation plan was executed correctly. Use when the user asks to verify completion, compare code changes to a plan, or produce a validation report. |
| documentation-lookup | developer-tools | Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). |
| verification-loop | workflow | A comprehensive verification system for Claude Code sessions. |
| strategic-compact | workflow | Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. |
| xp-code-review | practices | Review pending changes for tests, maintainability, and project rules. Use when the user asks for code review, review pending changes, or alignment with maintainability and project rules. |
| xp-increase-coverage | testing | Increase test coverage with high-value, behavior-focused tests. Use when the user asks to increase coverage, write tests for untested code, or add high-value tests. |
| xp-mikado-method | practices | Apply the Mikado Method for safe refactoring via a dependency graph of small steps. Use when the user asks for Mikado Method, safe refactoring, or dependency graph for a large change. |
| xp-plan-untested-code | testing | Plan tests for untested code with coverage gaps and risk-based prioritization. Use when the user asks for a test plan for untested code or coverage gaps. |
| xp-predict-problems | practices | Predict production failures and high-risk paths with a Lean/XP lens. Use when the user asks to predict failures, production risk, or edge cases. |
| xp-security-analysis | practices | Deep, pragmatic security review with OWASP and threat-modeling lens. Use when the user asks for security review, risk assessment, OWASP, or threat modeling. |
| xp-simple-design-refactor | practices | Refactor toward simple design and maintainability with ROI-driven prioritization. Use when the user asks to refactor, improve simple design, maintainability, or reduce accidental complexity. |
| xp-technical-debt | practices | Catalog and prioritize technical debt with a Lean/XP lens; top 5, quick wins, strategic debt. Use when the user asks for technical debt analysis, prioritization, quick wins, or tech debt payoff order. |
| cwv-improvement-planner | developer-tools | Build and prioritize Core Web Vitals improvement plans for web apps with a focus on LCP, INP, and TTFB. Use when users mention CWV, Lighthouse, PageSpeed, performance budgets, render blocking, hydration, image prioritization, CDN caching/compression, CloudFront, or Next.js web performance tuning. |
| test-doubles-first | testing | Select and implement the right test double with a default preference for fakes, stubs, and spies over mocks. Use when writing or refactoring tests, especially when users mention test doubles, mocking strategy, interaction assertions, or flaky tests caused by over-mocking. |
| planning-with-files | workflow | Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. |
| find-skills | ai | Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. |
| code-notify | developer-tools | Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. |
| github-host-alias | developer-tools | Use when running git clone, git remote add, or suggesting git commands interacting with GitHub to ensure the correct SSH host alias is used based on the local workspace path (~/work vs non-work paths). |
| lean-ai-adoption-coach | ai | Guide AI adoption decisions in software development using Lean, Extreme Programming, and pragmatic simplicity. Use when evaluating AI tools, agents, workflows, prompts, automations, or rollout guardrails. |
| pbt-pragmatic-adoption | testing | Pragmatic property-based testing review and first-wave adoption for this listings-webapp monorepo (Jest + fast-check, unit tests only). |
| skill-foundry | skill-governance | Design, organize, evaluate, benchmark, and improve portable Agent Skills. Use when creating a new skill, auditing a skill library, comparing a skill against baseline, optimizing descriptions, or retiring outdated skills. |