Orchestrate parallel judge agent execution, aggregate CaseScore results, write plan-judges.json, code-judges.json, prd-judges.json, or feature-judges.json, and validate output.
Orchestrate a structured software requirements discovery workflow that interviews stakeholders, builds or updates a canonical rupify-model, and generates a requirements spec,…
Expert in protecting projects from scope creep. Covers requirement management, stakeholder negotiation, saying no diplomatically, and keeping projects focused.
Interactive requirements elicitation for the Specification phase. Use when defining, reviewing, or modifying stakeholders, goals, user stories, requirements, assumptions, or…
R package for chromatin analysis. Use for single-cell ATAC-seq analysis, chromatin accessibility, and integration with Seurat.
Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria.
Applies Alex Hormozi's $100M Money Models frameworks to design, evaluate, and improve Skool community monetization strategies.
Applies Alex Hormozi's $100M Money Models frameworks to design, evaluate, and improve Skool community monetization strategies.
AI-Ready requirements specification generator that transforms vague ideas into professional specification documents deliverable to AI development tools (BMAD Story Format — from…
AI-Ready requirements specification generator that transforms vague ideas into professional specification documents deliverable to AI development tools (BMAD Story Format — from…
Greenfield-project onboarding skill. For a fresh repo (no CLAUDE.md, no forgeplan, no AGENTS.md), runs an active infrastructure setup (plugin gate → forgeplan MCP auto-wire via…
Turn current context, source references, and repo understanding into a complete product-grade PRD published as a GitHub issue.
Create a lightweight one-page solution pitch that summarizes the problem, proposed approach, alternatives considered, risks, success metrics, and effort estimate with a clear…
Модульный генератор PRD и SPARC документации (v2). Использует внешние скиллы через view() вместо встроенных копий: explore, goap-research-ed25519, problem-solver-enhanced.
Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step…
Validate spec bundle completeness — constitution, PRD, plan, tasks — and check alignment with SSOT, architecture docs, and target state
WRAPS gsd-spec-phase to make a phase's SPEC.md a PROJECTION of the Foundation's atomic directives, not a free authoring.
Detects when SPEC.md or PRD.md exceeds 300 lines and proposes feature-based splitting with a master route document.
spec.md 또는 prd.md를 분석하여 doc/plan.md와 Phase별 설계 문서를 자동 생성한다. 사용법: /spec-to-plan (현재 폴더의 spec.md 또는 prd.md를 자동으로 찾는다)
Turn the current conversation, repo understanding, and clarified decisions into a PRD. Use when a vague feature, client request, internal roadmap item, or discovery thread needs…
Master techniques for writing clear, complete product specifications and requirements documents (PRDs).
Specification-driven development toolkit integrating GitHub's Spec-Kit. Use when starting new projects, planning features, establishing development standards, or creating…
Specification-Driven Development (SDD) toolkit. Transforms ideas into executable specifications, implementation plans, and task lists.
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec. — from phamlongh230-lgtm/yamtam-engine
Translates a user request or PRD document into a structured Design Spec JSON — theme, color, typography, density, and device type.
Designs systematic investment products with transparent methodology, rebalancing rules, and index construction specifications.
Run Claude Code in autonomous iteration loops until task completion — PRD-based feature development, test coverage improvement, lint fixing, documentation generation, dataset…
UI development skill covering design token usage, shadcn/ui + Radix composition patterns, accessibility requirements, anti-patterns catalog, and brand context for…
Systematic approach to implementing features with detailed planning, tracking, and testing. Use when building new features, adding functionality to existing projects, implementing…
Use when the user says "write a spec", "create RFC", "write a PRD", or "document this decision". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.
Expert guidance for writing Product Requirements Documents (PRDs), helping product managers create clear, actionable specs that align engineering, design, and stakeholders.
Generate Playwright E2E test plan and specification documents from project artifacts (user stories, module models, mockups, specifications).
PRD驱动工作流的决策大脑 - 智能判断何时使用搜索、代码分析、多模型聚合。 作为子Skill被 th-prd-driven-dev-workflow 调用，负责工具选择和策略决策。
Project and feature planning with 4 adaptive phases - Specify, Design, Tasks, Execute. Auto-sizes depth by complexity.
Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues +…
Turn the current conversation context into a PRD and publish it as a GitHub issue that is ready to receive sub-issues from /to-issues-project.
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags.
Use Task Master AI when an agent needs to turn a product request or PRD into a dependency-aware task graph, expand or scope tasks, and keep implementation work anchored to an…
Use Spec Kit when an agent should turn a feature idea into a spec-first workflow with explicit artifacts, planning steps, and task breakdowns before code is written.
Generate PRDs, implementation plans, validation loops, issue investigations, and autonomous fix cycles inside Claude Code before coding starts.
Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy.
Validate and improve an implementation plan in plan mode by cross-checking with docs/design/*.md, docs/ROADMAP.md, docs/requirements.md, and src/. Superset of update-design.
Creates a reusable use case specification file that defines the business problem, stakeholders, and measurable success criteria for model customization, as recommended by the AWS…
[METHODOLOGY] User-spec creation through adaptive interview with codebase scanning and dual validation. Preloaded by dev-product-analyst agent.
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
Analyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system…
Tag new items in PRD.md files with unique ID codes and validate no duplicate tags exist. Applies to PRD.md documents structured with module sections containing User Stories, Non…
Validate a PRD for completeness, consistency, and implementation readiness. Use when the user says 'validate the PRD', 'review requirements', or 'is the PRD ready for development'.
Initiative-level PRD acceptance gate. Given a PRD ref/URL (GitHub Issue, Linear project/issue, Notion page, Confluence page, or JIRA issue), resolves the source vendor, reads the…
Use when you have a spec, feature request, or set of requirements that needs to be broken into vibe-kanban issues - decomposes the spec into an issue tree with dependencies,…
End-to-end pipeline that transforms an undocumented vibe-coded prototype into a Spec Kit-compatible specification package and a Superpowers-ready implementation handoff, including…
Clarify intent and freeze requirements by entering the canonical vibe runtime with a discovery-first bounded stop.
Browser-based visual companion for brainstorming sessions — showing mockups, wireframes, diagrams, and side-by-side comparisons.
Examines a specific product's detailed page to verify it matches the user's requirements, checking price, description, features, and reviews.
Evaluates product listings against user requirements such as price limits and feature matches to identify viable options.
Use when gathering or interpreting requirements, estimating effort, or communicating with stakeholders/customers about what to build
Primary pipeline shaping step after /research and before /prd-to-issues. Use when the problem is understood well enough to turn into a bounded PRD issue.
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their…
Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ, acceptance criteria, rollout plan).