Skills publicadas
Mostrando 12 de 14customer-research
Customer research and problem framing using the research-design discipline: hypothesis, null hypothesis, MECE questions, methods, findings. Produces Pyramid-base-shaped output ready for downstream composition into PR/FAQs, long-form narratives, or PRDs. Use when the user asks to design user research, run customer interviews, synthesize research findings, frame a problem statement, build a customer
tech-stack-builder
Optional initial project context (e.g., "Python API for payments on AWS")
ultraplan
The problem to plan. One or two sentences is enough.
erpaval
Workflow for autonomous software development with Claude Code. Classifiers route scope, complexity, directory state, and spec readiness before committing to Explore / Research / Plan / Act / Validate, then close the loop with a Compound step that persists lessons to `.erpaval/solutions/` for future sessions. Optional HMW reframing and EARS specification add structured rigor — Claude judges when to
product-design-shared
Shared canonical references for product-design frameworks — Pyramid Principle, Working Backwards, Double Diamond, research design, methodology selection. Consumed by `product-discovery`, `product-strategy`, `working-backwards`, and `customer-research` via `${CLAUDE_PLUGIN_ROOT}/skills/product-design-shared/references/`. Do NOT invoke this skill directly — it has no orchestrator and no templates. L
meta-prompt-optimizer
Audit and rewrite prompts against Claude Opus 4.7 instruction-following best practices. Produces a scored audit plus a rewritten prompt. Use when the user asks to audit, review, critique, rewrite, improve, optimize, tighten, score, fix, migrate, or draft a prompt — including system prompts, CLAUDE.md files, Claude Code agent definitions, slash commands, SKILL.md files, Jinja2 prompt templates, or
research
The research topic or question.
working-backwards
Working Backwards 5-stage customer-first product discovery. Orchestrates Listen, Define, Invent, Refine, Test & Iterate to produce a 5CQ, PR/FAQ, or Dear Customer Letter. Use when the user asks to work backwards, write a PR/FAQ, draft 5 customer questions, do customer-first product definition, or mentions Working Backwards, press release FAQ, 5CQ, MLP, or customer obsession. Do NOT use for strateg
product-strategy
Optional ask, prior memo path, or challenge statement.
erpaval
Workflow for autonomous software development with the Kiro CLI (open Agent Skills standard). Classifiers route scope, complexity, directory state, and spec readiness before committing to Explore / Research / Plan / Act / Validate, then close the loop with a Compound step that persists lessons to `.erpaval/solutions/` for future sessions. Optional HMW reframing and EARS specification add structured
product-discovery
File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or discovery memo, and runs a critic pass. Absorbs prd-drafter (idea to PRD via thr
agent-ux-patterns
Agent UX patterns and human-in-the-loop design: Twilio A2H protocol, Levels of Autonomy (L0-L5), inbox pattern, progressive trust, decision journal, gate reviews, autonomous work reports. Six-phase methodology from vague pain point to concrete data model via landscape research and multi-direction brainstorming. Use when the user asks to design agent UX, pick an autonomy level, build a human-in-the