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…
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
Make a short video about a product or brand (promo, launch, explainer, demo or social clip) entirely in code with Remotion, from idea to a rendered MP4 with sound. The owner approves the idea and a storyboard before anything is built.
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.
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.
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.
A workflow guide for OpenPrd, a workspace for turning unclear product ideas into clarified requirements and a handoff for implementation. It helps choose and run each stage, from questions through final handoff.
A detailed product-requirements-document writer for regulated, financial, risk-management, and cross-functional projects. A PRD is a shared plan that explains what a product must do, who it serves, how it will be accepted, and what happens during release.
Clarify, create, review or change product, service and office workflow requirements, PRDs and interactive prototypes. Use for vague goals, process improvements, spreadsheet/form rules, small UI edits and changes to existing systems, even without the word requirement.…
A guided process for discovering a product idea and writing a PRD, or product requirements document. A PRD records what should be built, for whom, and how it should work.
Generate Codex-first agent context files for a Web MVP. Use after the PRD and Technical Blueprint exist when the user needs AGENTS.md, REVIEW-CHECKLIST.md, and agentdocs for project brief, requirements, tech stack, page map, data model, build tasks, testing, and reusable prompts.
The antidote to vibe coding: a full software engineering team at your fingertips. Create or reverse-engineer PRDs, TRDs, personas, epics, and user stories with acceptance criteria, then plan, implement, test, and verify code against them - plus an autonomous Goal-Driven sprint loop that drives a prioritised batch to a…
A set of rules and templates for creating and reviewing product design documents in the ued/ directory. It covers documents ranging from strategy and requirements to architecture, detailed design, and validation.
Skill-first run-through feature workflow for Claude, Codex, and Gemini. Use when the user asks to implement a feature through PRD, TechSpec, Tasks, verification, local commit, and branch handoff. The npm package installs skill files only; the LLM skill performs the workflow.
Use when the user asks for deep business review of PRDs, requirement documents, product specs, feature proposals, or business process docs. Focus on understanding business model, modules, data relationships, flows, permissions, states, rules, omissions, contradictions, ambiguities, implementation risk, and…
Full PRD creation pipeline — research, draft, review, and senior-PM judgment with human gates between phases. Chains researcher → prd-writer → prd-reviewer → prd-senior-pm agents.
A conversation guide for turning an unclear product idea or feature request into a structured product decision. It emphasizes confirming the target market, checking real user need, and looking for contrary evidence.
A planning guide for turning an AI product idea into a written product architecture. It organizes the idea around users, situations, capabilities, and data, then explains how information moves through the product.
Use this skill when the user has a product idea, feature concept, startup direction, vague requirement, or asks for a PRD before the idea is clear. Run a ruthless pre-launch clarification workflow: first challenge user/problem/value/MVP as a senior product manager, then challenge market/business/growth/ROI as a…
★not rated 3 3mo agoA86 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: