Create comprehensive Product Requirements Document with structured elicitation and adversarial review (Codex skill for /ensemble:create-prd)
Adds new requirements to an existing PRD with interactive refinement and task generation. Supports file paths and URLs in requirement description.
Business analysis: requirements engineering, stakeholder analysis, process modeling.
Viết MỚI đặc tả nghiệp vụ trên FARE — Use Case, User Story, BRD/SRS/PRD/requirement (richtext) và Glossary — từ một yêu cầu nghiệp vụ.
Feature Design Document (FDD) methodology for structured feature development. Three-phase approach: Statement of Intent → Feature Requirements → Feature Realization.
Guided feature development from requirements to deployed code. Combines codebase exploration, architectural design, parallel implementation via DAG orchestration, and quality…
Tool-agnostic feature design preflight that traces a requirement through production constraints, dependencies, user and system flows, edge cases, security, operations, and tests…
Orchestrate end-to-end feature development from requirements through implementation, testing, and review.
Create clear feature documentation for non-professional developers. Use PROACTIVELY when documenting new features, significant code changes, creating technical specifications, or…
Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for…
Write a feature flag management guide and lifecycle playbook for a service or team — covering flag taxonomy, creation checklist, rollout strategy, monitoring requirements, cleanup…
Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation c — from…
Convert PRD requirements into structured epics, features, and user stories with acceptance criteria and priority rankings
Plan feature implementation with technical specifications and actionable steps for solo developers
Creates a complete product feature specification with acceptance criteria, scope, dependencies, and risks. Delegates to the Prometeo (PM) agent.
Draft detailed engineering specs from an approved PRD. Use when generating or updating the engineering specification for a feature, before implementation begins.
Review and score engineering specs against a startup-focused quality rubric. Penalize over-engineering and reward simplicity.
Turn a feature request or bug cluster into a source-backed spec, impact map, acceptance criteria, and delivery plan before coding.
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
Create feature spec files from project docs, commit and push to main, and create matching feature branches from main. — from product/prd-spec
Create feature spec files from project docs, commit and push to main, and create matching feature branches from main. — from majiayu000/claude-skill-registry
Reviews feature specifications for completeness, testability, and implementation readiness. Validates acceptance criteria, edge cases, and technical constraints.
Feature specification structure, API contract patterns, and state definition templates. Use when writing implementation-ready feature specs that development agents can execute…
Creates focused feature specifications with user stories, acceptance criteria, and edge cases. Lighter than PRD, focuses on single feature implementation.
Style rules and anti-patterns for writing PRDs — every acceptance criterion must name its verification artifact; paired good/bad examples for the common drift modes.
"PRD 작성", "기획서", "제품 기획", "product requirements", "아이디어 구체화", "서비스 기획", "feasibility", "실현 가능성", "API 조사", "기술 스택 추천", "경쟁사 분석", "수익 모델" 등 아이디어를 PRD 문서로 변환할 때 사용하세요.
Agent-to-Agent (A2A) Protocol RC v1.0 bridge for OpenClaw agents. Enables agent discovery, identity cards, task lifecycle management, push notification configuration, task…
Use when scoring a list of business or solution requirements against the *actual* capabilities of a specific Salesforce org so each row can be classified Standard / Configuration…
Cria Especificações Técnicas de Frontend a partir de um PRD e de um API Contract obrigatório. Use esta skill sempre que o usuário quiser criar a tech spec do frontend, definir…
Cria Especificações Técnicas detalhadas e prontas para implementação a partir de um PRD existente, com detecção automática de modo de operação (Standalone, Pipeline ou API-First).
Generates accessible focus indicators meeting WCAG 2.4.7 and 2.4.11 requirements. Use when styling :focus-visible, keyboard navigation indicators, or fixing focus ring visibility…
Create a requirements PRD for a feature through structured interview. Use when user runs /feature-forge:forge-1-prd or explicitly asks to start the forge pipeline for a new…
Conducts comprehensive frontend design reviews covering UI/UX design quality, design system validation, accessibility compliance, responsive design patterns, component library…
Breaks down high-level game ideas into technical specifications and a feature roadmap.
Build enhancer-driven gene regulatory networks (eGRNs) by integrating single-cell RNA-seq and ATAC-seq using SCENIC+, CellOracle base GRNs, Pando, FigR, DIRECT-NET, TRIPO — from…
Generates features_spec.txt files for use with auto-code extension mode. Analyzes existing codebase and creates structured feature specifications based on user requirements.
Generates a detailed, step-by-step developer task list in Markdown format from a Product Requirements Document (PRD).
Generates production-grade TaskMaster tasks.json from Product Requirements Documents (PRD). Activates via codeword [ACTIVATE:PRD_TO_TASKS_V1] injected by hooks when PRD is…
Use when generating PRD and architecture documents that must trace back to explicit decisions. Enforces citation requirements so no spec content exists without DEC-* references.
Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous…
Scans a GitHub repository for issues carrying the configured `ready` PRD label and runs the first eligible one through the dry-run validation pipeline.
Use when (1) breaking down a feature request into implementable tasks, (2) creating a detailed feature specification, (3) preparing work for development.
Decomposes a product specification into ordered features with dependencies, tracks progress, and drives sequential execution through the go-hexagonal pipeline.
Transforma los artefactos de un proyecto GSD (Get Shit Done) en un PRD sintético compatible con /prd-quality-guard.
Analyze gspec/ documents for discrepancies and contradictions across profile, stack, style, practices, architecture, and features.
Transformiere explorative Artefakte — Code-Repos, Excel-Dateien, JSON, CSV, SQL — in ein reviewbares, übergabefähiges Spezifikationspaket für formale Software- oder…
Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability,…
Use when when exporting quantified MSI data (feature-by-pixel intensity matrices with associated ion m/z, lipid annotations, and pixel spatial coordinates) from LipidQMap and you…
HTML standards for Oh My Brand! theme. Semantic elements, accessibility requirements, ARIA attributes, and attribute best practices.
Team Lead: reads task DAG, dispatches up to 4 parallel agents with Ralph-style TDD and backpressure gates. Run after /prd-tasks.
Use when a user needs to develop an idea through discovery, refinement, validation, specification, and execution readiness for a product, feature, workflow, SaaS, AI tool,…
Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics.
Use when positioning an IJCAI or IJCAI-ECAI submission against archival AI literature, arXiv preprints, workshop papers, prior rejected versions, dual-submission rules, shortened…
Breaks a PRD or RFC into small, well-scoped implementation tasks suitable for individual pull requests. Use when translating product requirements into engineering work items.
Master orchestrator that generates all implementation specs (PRD, Architecture, UX, Implementation, Test, Release) from product plan.
Use when starting a new session without feature-list.json, setting up project structure, or breaking down requirements into atomic features. Load in INIT state.
Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.
Use when when you have aligned paired scATAC-seq and scRNA-seq data from the same cells (multiome data) and need to create a single reduced-dimension coordinate space that…
Symmetric counterpart to notion-prd-intake on the JIRA side. Scans a JIRA project (or JQL filter) for tickets in the configured `ready` status, claims the first eligible — from…
Use when defining a feature, writing a PRD, or scoping work - reframes requirements around the user's job instead of the feature or team that owns it.