fimoklei/pm-ai-playbook

intent-layer

Use when initializing or maintaining agent-friendly repo context, setting up AGENTS.md or CLAUDE.md, adding local rules, defining verification commands, or checking whether context files are stale.

원문 언어: 영어

workflow-ship

Use when the user asks to run workflow:ship, ship a branch, publish a feature branch, open and merge a PR, or push/PR/merge/cleanup completed work.

원문 언어: 영어

workflow-commit

Use when the user asks to run workflow:commit, create a commit, make a git commit, stage changes, write a commit message, or prepare local changes for shipping.

원문 언어: 영어

47

Turn any rough prompt, half-formed idea, or task description into a finished, ready-to-send prompt optimized for Opus 4.7 (with adaptive thinking) inside the chat app — claude.ai, the Mac app, the iOS app — NOT the API. Use this skill whenever the user wants…

원문 언어: 영어

kiro-discovery

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

원문 언어: 영어

kiro-intent

Pre-discovery intent exploration for genuinely vague ideas. Use when the user pitches an idea where the real user-need, problem framing, or core assumptions are unclear — before /kiro-discovery. Delegates to the intent-explorer skill, which produces…

원문 언어: 영어

six-hats

Structured six-hats thinking sessions for debating decisions. Use when user says "six hats", "six hats debate", or wants to explore a decision through six colored-perspective lenses in sequential rounds with a final recommendation.

원문 언어: 영어

codedocs

Use this skill when generating AI-agent-friendly documentation for a git repo or directory, answering questions about a codebase from existing docs, or incrementally updating documentation after code changes. Triggers on codedocs:generate, codedocs:ask,…

원문 언어: 영어

skill-audit

Use this skill when auditing AI agent skills for security vulnerabilities, prompt injection, permission abuse, supply chain risks, or structural quality. Triggers on skill review, security audit, skill safety check, prompt injection detection, skill trust…

원문 언어: 영어

cross-pollination-engine

Systematically borrow ideas from unrelated industries to solve problems. Innovation often comes from adjacent fields. Use when user says "cross-pollination", "how would X solve this", "borrow ideas from", "what can we learn from", "think outside the box",…

원문 언어: 영어

first-principles-decomposer

Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method",…

원문 언어: 영어

intent-explorer

Use when starting a new feature, product idea, or problem exploration and the real user need is unclear. Trigger on "intent", "explore intent", "intentspec", "what should we build", "what's the real problem", "explore this idea", "user research", "discovery",…

원문 언어: 영어

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js…

원문 언어: 영어

idea-challenger

Pre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment. Use when evaluating new products/features/strategies, before significant resource allocation, when stakeholders seem overly optimistic, or when…

원문 언어: 영어

verification-before-completion

Run verification commands and confirm output before claiming success

원문 언어: 영어

security-threat-model

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path,…

원문 언어: 영어

six-thinking-hats

Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing…

원문 언어: 영어

inversion-strategist

Flip problems upside down - instead of "how to succeed", ask "how to definitely fail" then avoid those paths. Use when user says "invert", "inversion", "flip it", "opposite approach", "how would this fail", "avoid failure", "what NOT to do", "Munger",…

원문 언어: 영어

pre-mortem-analyst

Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before…

원문 언어: 영어

collision-zone-thinking

Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"

원문 언어: 영어

inversion-exercise

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

원문 언어: 영어

meta-pattern-recognition

Spot patterns appearing in 3+ domains to find universal principles

원문 언어: 영어

root-cause-tracing

Systematically trace bugs backward through call stack to find original trigger

원문 언어: 영어

scale-game

Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales

원문 언어: 영어

simplification-cascades

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

원문 언어: 영어

when-stuck

Dispatch to the right problem-solving technique based on how you're stuck

원문 언어: 영어

skill-creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

원문 언어: 영어

the-challenger

Pre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment. Use when evaluating new products/features/strategies, before significant resource allocation, when stakeholders seem overly optimistic, or when…

원문 언어: 영어

optimize-docs

Condense markdown documentation for token efficiency while preserving all semantic meaning. Use when rules, documentation, or config files need optimization. Target 25-40% reduction through systematic condensation patterns.

원문 언어: 영어

jtbd-analyzer

Uncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations. Use when user says "jobs to be done", "jtbd", "why do customers", "what job", "customer motivation", "what problem",…

원문 언어: 영어

backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

원문 언어: 영어

frontend-patterns

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

원문 언어: 영어

session-summarizer

Use when user runs /summarize command to capture session knowledge

원문 언어: 영어