Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…
Execute the next TaskMaster task using the implementation plan with CDD verification. Picks the next ready task, matches it to the plan step, implements via a dispatched subagent, verifies subtasks with evidence, marks the task done, and loops until every task is complete. Wraps the TaskMaster next -> in-progress ->…
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…
Refactor high-complexity React components in frontend. Use when the user asks for code splitting, hook extraction, or complexity reduction, or when you come across a component that is too complex to understand and refactor it.
Generate Vitest + React Testing Library tests for frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization. Use when writing, reviewing, or refactoring vitest tests, or when user mentions vitest, testing, TDD, test coverage, mocking…
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over…
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.
Create or update a lean, user-centered living Product Requirements Document through repeated drafting and subtraction. Use when defining a feature or interface, planning root-cause or architectural work, revising implementation as discoveries emerge, handling legacy migration, or removing speculative scope and…
Review implementation against its purpose and user experience, fix root causes, and refine it through repeated simplification passes. Use when verifying correctness and side effects, reviewing user-facing or developer-facing interfaces, redesigning flawed foundations, managing legacy compatibility, removing…
A quality-checking agent for outputs created by other skills in the vibe-coding-kit. It reads project rules and checks documents for required content and consistency.
An interview-style requirements assistant that turns an unclear product idea into a practical product requirements document, or PRD. A PRD explains what a product should do well enough for development to begin.
A requirements guide for using AI to build software from an idea, including demos and longer-term products. It helps describe what should happen, who it is for, and the limits of the work.
Analyze competitive landscape with feature matrices, positioning maps, and strategic gap analysis. Use when asked to analyze competitors, map the competitive landscape, find differentiation, or evaluate alternatives to a product.
Analyze customer motivations using Jobs-to-be-Done and Forces of Progress. Use when asked about jobs-to-be-done, why customers switch products, what job a product is hired for, or when analyzing the forces that drive or resist product adoption.
Map opportunities using Teresa Torres' Opportunity Solution Trees. Use when asked to identify opportunities, find product gaps, explore new areas, map the solution space, or connect business outcomes to customer needs and testable solutions.
Activate this skill when the user wants to create, update, validate, or review a Product Requirement Document. Triggers on mentions of PRD, product requirements, user stories, acceptance criteria, or initiative documentation, or when the user describes a feature and asks for structured documentation.