Feature requirements en architectuur definiëren. Gebruik bij /dev-define [feature-name] om een feature te specificeren voor de build-fase.
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding.
Fase 2: Crea il Product Requirements Document. Usa questa skill quando l'utente vuole creare il PRD, definire requisiti, personas, priorita MoSCoW, o dice fase 2, PRD, requisiti…
Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document.
Expand user requirements into detailed DevDocs documents. Use when users provide feature requirements, want to clarify requirements, or need to create product requirement…
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.
Find differentially accessible chromatin regions between conditions using DiffBind or DESeq2. Use when comparing chromatin accessibility between treatment groups, cell ty — from…
Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets.
Director of Product Management - assign roadmap, requirements governance, and team coordination tasks
Discovery-first development workflow. Use BEFORE creating worktrees for any non-trivial feature. Explores requirements through questions, proposes approaches, validates design…
Lifecycle'ın "A"sı — INVEST user story, acceptance criteria (Gherkin Given/When/Then), assumption tracking, NFR (latency/availability/scale), non-goal tanımı, risk + open…
Creates Product Requirements Documents (PRDs) from feature requests following a structured workflow of clarification, planning, and drafting.
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases.
Documentation creation criteria including PRD, ADR, Design Doc, and Work Plan requirements with templates.
Generate professional Product Requirement Documents (PRD) from multiple sources — Figma designs, briefs, user research, existing code.
Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done.
Use when the user says "draft a design doc for {feature}" / "write an RFC for {feature}" / "design this before I build it" — produces a full design doc with Context, Goals,…
Generate tight, one-page PRDs for CustomGPT.ai Labs projects aligned to Why/How/What, success metrics, and fast experimentation constraints.
PRD를 입력하면 디자인 시스템 컴포넌트 인스턴스 기반으로 Figma 화면 3개 안을 자동 생성하는 스킬. 비 디자이너가 빈 Figma 파일에서 바로 사용 가능.
Hub skill for requirements elicitation. Provides technique selection, orchestration guidance, LLMREI patterns, and autonomy level configuration.
Generates structured summaries of U.S. energy sector regulations and landmark cases with compliance-focused analysis.
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…
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…
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.
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 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.