WRAPS gsd-spec-phase to make a phase's SPEC.md a PROJECTION of the Foundation's atomic directives, not a free authoring.
Public workflow entrypoint (spec-prd): create, write, refine, or validate planning-readiness of brownfield PRD-grade requirements for existing systems before implementation…
Run a structured quality audit on a product spec, PRD, or requirements document. Produces a severity-rated issue list with concrete fixes — catches untestable requirements,…
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…
Create implementation tickets with dependency graphs, Independent/Collaborative classification, and context pointers from a spec, PRD, or conversation context.
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.
Use when creating design diagrams, diagram packs, architecture diagrams, ER diagrams, sequence diagrams, swimlane diagrams, business flows, data flows, deployment diagrams, state…
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.
Run a structured, business-value-first product-planning interview that turns a fuzzy idea into a build-ready spec — BEFORE any code is written.
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…
Requirements phase — a clarifying, options-first stakeholder interview that removes confusion and assumptions (not a relentless grilling) and produces a validated SRS +…
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 调用，负责工具选择和策略决策。
Execute DSDS roadmap tickets using dependency-aware, acceptance-criteria-first delivery. Use when selecting the next unblocked ticket, implementing code changes, validating…
Turns decided work — a PRD, design doc, RFC, or thread — into tasks a builder can act on without guessing.
Project and feature planning with 4 adaptive phases - Specify, Design, Tasks, Execute. Auto-sizes depth by complexity.
Use when you have aligned ATAC-seq BAM files from Tn5-based chromatin accessibility assays and need to perform footprinting analysis.
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.
Turn the current conversation into a spec (PRD) and publish it to the project's issue tracker — no interview, just synthesis of what was already discussed, with Laravel test seams…
The new-feature flow of taskplane — use when the goal is to BUILD something new: 'build a new feature', 'add X to the app', 'prototype this idea', 'build it as A/B variants',…
The product persona of taskplane — owns the WHAT. Use for anything about what to build and whether it's the right thing: 'spec this', 'write acceptance criteria', 'refine the…
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags.
Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements.
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.
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction…
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…
Cold-start unpacker for vague boss/business requirements. Use when the user says "老板/业务只给了一个模糊方向", "帮我接一下这个需求", "信息不全先拆一下", "我还没 PRD 先给方案骨架", or needs a 30-minute to 2-hour PM…
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,…
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create…
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.
Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`.
Browser-based visual companion for brainstorming sessions — showing mockups, wireframes, diagrams, and side-by-side comparisons.
Gorgeous/cinematic requirements every delivered app's UI must meet — anti-slop premium bar, exact brand tokens, motion, logo/image quality, WCAG 2.2 visual accessibility.
Walmart product detail page extractor: given a walmart.com product URL (walmart.com/ip/...), extract full product data including itemId, title, brand, model, UPC, price, wasPrice,…
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