Phase 1 of spec-driven development — generate spec.md from a problem statement. Requirements, user stories, acceptance criteria. No implementation details.
Autonomous batch task execution with PRD parsing, task decomposition, and continuous execution until all tasks complete. Uses /orchestrator internally.
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation.
End-to-end ATAC-seq workflow from FASTQ files to differential accessibility and TF footprinting. Covers alignment, peak calling with MACS3, QC metrics, and optional TOBIA — from…
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to…
Create architecture documentation and ADRs from PRD requirements
GLAW Tax & IRS Division strategist — turns a company's facts into a FULL tax-credit & incentive strategy DOSSIER (business-plan style): an executive thesis, a benefit-by-benefit…
Train + validate a speculative-decoding draft head (EAGLE3 or DFlash) for an ARBITRARY target LLM, generalizing the GLM-5.1-only SpecForge recipe so any new model gets one.
Turns an already-interrogated plan into a committed PRD — a WHAT-only specification of what an Initiative delivers — written to `docs/prds/.md`.
Use when: 需要将需求转化为用户故事、准备敏捷开发任务、进行需求拆分、编写验收标准 Do NOT use when: 需求已可直接进入开发、团队不使用用户故事格式
Review Product Overview Documents for completeness, clarity, source-of-truth conflicts, module-boundary drift, and likely downstream FRD / Blueprint / Work Order impact.
Smart PRD generator with TaskMaster integration. Detects existing PRDs and offers execute/update/replace options.
Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting…
Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility,…
Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption.
PRD Structural Validator. Reads a PRD and checks it against the required structure checklist. Outputs a pass/fail validation report without modifying the PRD.
PRD 생성 전체 워크플로우를 자동화한다. 대화 → 시나리오 → 레퍼런스 → PRD → 다이어그램 → 태스크.
Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research.
Interactive question-driven discovery skill that transforms vague business problems into structured AI-consumable documents.
Use when writing a PRD from a Linear ticket or feature request. Triggers on "write PRD", "create requirements doc", "PRD from ticket".
Use when: writing, rewriting, or auditing acceptance criteria, definition-of-done lists, or user-story AC for quality: testable, observable, single, scoped, and…
**DEFAULT for concept-stage thinking — produces a structured concept brief (problem, target users, proposed approach, key differentiator, success criteria, top risks, validation…
Generate a personalized Second Brain PRD from a completed requirements template. Use when the user has filled out my-second-brain-requirements.md and wants to generate their build…
Creates a Product Requirements Document through interactive brainstorming with parallel codebase and web research.
ALWAYS use when extracting functional specifications from existing code that lacks documentation. Supports two perspectives: (1) product-feature specs that analyze multiple source…
Pre-implementation cross-artifact consistency sweep — checks PRD↔TRD↔beads alignment before coding begins (Codex skill for /ensemble:analyze-requirements)
Create Technical Requirements Document from PRD with architecture design and adversarial review (Codex skill for /ensemble:create-trd)
Create Foreman-native structured Technical Requirements Document from PRD — omits adversarial review phase, outputs parser-compatible tables (Codex skill for…
Pre-implementation traceability gate — validates REQ-NNN coverage and TEST task pairing between PRD and TRD (Codex skill for /ensemble:validate-requirements)
Interactive Product Owner / Product Architect session for discussing and designing a new feature. Analyzes existing codebase, suggests solutions and alternatives, and produces a…
Deep requirements elicitation using structured questioning techniques. Use when the user wants to explore requirements gaps, validate assumptions, and discover unstated needs…
Generates complete PRD document from business requirements. Creates use case diagrams, requirements analysis (UR/FR/NFR), SysML diagrams, and complete PRD file.
Discover and pin down what to build before building it, with a gated five-stage flow: elicit the real need (not the stated solution), analyze and prioritize, write verifiable…
Render derived artifacts from the Innovation Canvas Document. Produces the two-page executive summary, an extracted decision log, the artifact specification handoff, or a status…
Orchestrator of the Karvey Method — the complete spec-driven development (SDD) pipeline, stack-agnostic.
Pre-spec interrogation. Interviews the engineer relentlessly about their problem before writing any spec. Use at the start of every new feature or initiative — before karvey-init.
Convert existing specs from Kiro (cc-sdd) or gstack into the Karvey method's `docs/spec/` structure. Maps requirements/design/tasks into Karvey's prd.md, requirements.md,…
Initialize a new Karvey spec. Creates the directory structure, spec.json, and registers the Epic in ClickUp (or PLAN.md if not using ClickUp).
Generate a navigable HTML mockup with 3–4 levels of depth from approved requirements, then validate it against the requirements to catch spec-gaps early.
Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes.
Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the work of the previous.
Plan a WordPress plugin through a structured discovery conversation. Asks questions to uncover requirements, blind spots, and edge cases, then produces a PRD markdown file.
**DEFAULT for PRD FOR AN AI/LLM/AGENT FEATURE — model selection rationale, eval plan, safety boundaries, cost envelope, failure-mode map: PRD covering AI-specific sections (model…
Transforme des inputs bruts en un PRD structuré et crée la page Notion correspondante. Utiliser quand l'utilisateur mentionne "PRD", "spec", "feature à spécifier", "brief…
**DEFAULT for early-stage thinking that doesn't yet warrant a full PRD — produces a 1-2 page structured product doc with problem, users, goals, scope, success criteria.**…
**DEFAULT for any product change crossing teams or with meaningful complexity — produces a full structured product doc with problem, users, goals, non-goals,…
**DEFAULT for infrastructure work, platform features, developer tools, or any product where technical shape is the primary risk — produces a PRD oriented around technical design…
Decomposes a PRD, issue, or spec into a copy-pasteable `/goal until ... abort-if ...` line. Use when running /goal against a spec, to reduce acceptance criteria to AND-joined…
Update a specific section of PRD.md and sync changes to feature_list.json if features are affected.
Prioritize which specs to write first from product + engineering definitions. Triggers: 'spec roadmap', 'what to spec first', 'prioritize features', 'spec backlog'.
Write a product specification (PRD) from a validated idea or feature request. Use when the user needs to define requirements, user stories, acceptance criteria, or technical…
Draft a product spec (PRD) for a feature or initiative, pulling context from Notion, Slack, and Drive first so the draft isn't starting from zero.
Convert any MCP (Model Context Protocol) server into a standalone CLI utility and auto-generate companion skill documentation through an 8-phase workflow with structural anti-skip…
Walk a spec bundle section by section to mutual understanding, producing the signed-off kickoff brief that downstream skills execute from.
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios — from…
Use when you need the GitHub CLI (`gh`) to verify installation, list issues (all or by milestone) as markdown tables, fetch issue bodies and comments for analysis, or han — from…
Erstellt leichtgewichtige HTML-Mockups und eine visuelle Sitemap vor dem Requirements Engineer. Input ist das ausgewaehlte Wireframe/Layout aus visual-companion plus optional…
Knowledge pack for writing Given/When/Then acceptance criteria that are unambiguous and automatable. Auto-loaded by product-agent (writing) and test-agent (consuming).
Use when reviewing accessibility of websites, apps, or facilities, conducting WCAG audits, preparing for ADA Title II/III deadlines, or checking digital/physical accessibility…
Document feature requirements - creates/updates about.md with business rules, scope, decisions