pm-ai-playbook

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.

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.

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.

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 to write, rewrite, optimize, improve, sharpen, or polish a prompt for the chat app. Trigger phrases include "rewrite this prompt", "make this a better prompt", "optimize this prompt", "turn this into a prompt", "help me prompt this", "draft a prompt that...", "I want to ask...", or whenever the user pastes a draft prompt and asks for improvements. Also trigger when the user describes a task they plan to send into the chat app and clearly wants a reusable, well-structured prompt rather than a direct answer. The output is always a single, copy-pasteable prompt in a code block that the user sends as-is — never a template with placeholders. Always ends with the exact line "Think before answering (maximum reasoning)".

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.

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 .kiro/specs/<slug>/intent-spec.md. The output is auto-detected by /kiro-discovery and downstream spec skills, so the user does not need to pass intent context as an argument. Skip this skill entirely when the user already has a clear problem statement.

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.

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, codedocs:update, "document this codebase", "generate docs for this repo", "what does this project do", "update the docs after my changes", or any task requiring structured codebase documentation that serves AI agents, developers, and new team members.

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 verification, skill quality gate, and any task requiring security analysis of AI agent skill files.

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", "how would Disney/Apple/Amazon do this", "different industry", "steal ideas".

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", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.

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", "requirements grounding", or before any specification work.

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 pages, data fetching, bundle optimization, or performance improvements.

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 cost of failure would be high (reputation, budget, market position).

Run verification commands and confirm output before claiming success

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, enumerate threats/abuse paths, or perform AppSec threat modeling.

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 discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).

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", "anti-goals", "guarantee failure".

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 we launch", "stress test", "what would kill this", "project risks".

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

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

Spot patterns appearing in 3+ domains to find universal principles

Systematically trace bugs backward through call stack to find original trigger

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

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

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

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.

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 cost of failure would be high (reputation, budget, market position).

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.

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", "user needs", "why do people buy".

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

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

Use when user runs /summarize command to capture session knowledge