fimoklei/pm-ai-playbook
56 skills · 549 total installs
$npx skills add fimoklei/pm-ai-playbookSkillInstalls
first-principles-decomposerBreak any problem down to fundamental truths, then rebuild solutions from atoms up.optimize-docsCondense markdown documentation for token efficiency while preserving all semantic meaning. Use when rules, documentation, or config files need optimization.idea-challengerPre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment.inversion-strategistFlip problems upside down - instead of "how to succeed", ask "how to definitely fail" then avoid those paths.pre-mortem-analystImagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain.security-threat-modelRepository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise…backend-patternsBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.collision-zone-thinkingForce unrelated concepts together to discover emergent properties - "What if we treated X like Y?jtbd-analyzerUncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations.karpathy-guidelinessimplification-cascadesFind one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Zwhen-stuckDispatch to the right problem-solving technique based on how you're stuckcross-pollination-engineSystematically borrow ideas from unrelated industries to solve problems. Innovation often comes from adjacent fields.frontend-designinversion-exerciseFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?meta-pattern-recognitionSpot patterns appearing in 3+ domains to find universal principlessession-summarizerUse when user runs /summarize command to capture session knowledgesix-thinking-hatsApply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis.skill-creatorvercel-react-best-practicesReact and Next.js performance optimization guidelines from Vercel Engineering.frontend-patternsFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.scale-gameTest at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scalesverification-before-completionRun verification commands and confirm output before claiming successwriting-clearly-and-conciselyintent-explorerUse when starting a new feature, product idea, or problem exploration and the real user need is unclear.root-cause-tracingSystematically trace bugs backward through call stack to find original triggerthe-challengerPre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment.codedocsUse this skill when generating AI-agent-friendly documentation for a git repo or directory, answering questions about a codebase from existing docs, or…grill-meskill-auditUse this skill when auditing AI agent skills for security vulnerabilities, prompt injection, permission abuse, supply chain risks, or structural quality.diagnoseDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test.grill-with-docsGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as…improve-codebase-architectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.six-hatsStructured six-hats thinking sessions for debating decisions. Use when user says \"six hats\", \"six hats debate\", or wants to explore a decision through six…47Turn 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…intent-layerUse when initializing or maintaining agent-friendly repo context, setting up AGENTS.md or CLAUDE.md, adding local rules, defining verification commands, or…thermo-nuclear-code-quality-reviewworkflow-commitUse 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.workflow-shipUse 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.defense-in-depthValidate at every layer data passes through to make bugs impossiblee2e-testingComprehensive end-to-end testing command. Launches parallel sub-agents to research the codebase (structure, database schema, potential bugs), then uses the…kiro-debugInvestigate implementation failures using root-cause-first debugging.kiro-discoveryEntry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed)…kiro-implImplement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.kiro-intentPre-discovery intent exploration for genuinely vague ideas. Use when the user pitches an idea where the real user-need, problem framing, or core assumptions…kiro-reviewReview a task implementation against approved specs, task boundaries, and verification evidence.kiro-spec-batchCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.kiro-spec-designGenerate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.kiro-spec-initInitialize a new specification with detailed project descriptionkiro-spec-quickQuick spec generation with interactive or automatic modekiro-spec-requirementsGenerate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.kiro-spec-statusShow specification status and progresskiro-spec-tasksGenerate implementation tasks from requirements and design. Use when creating actionable task lists.kiro-steeringMaintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.kiro-steering-customCreate custom steering documents for specialized project contexts. Use when creating domain-specific steering files.kiro-validate-designInteractive technical design quality review and validation. Use when reviewing design before implementation.