Навыки: Данные

Generate comprehensive Product Requirements Documents from structured inputs. Apply company templates, create technical...

Rigorous engineering planning and PRD implementation standards. Use when creating implementation plans, working through...

Bridges approved PRDs to implementation by mapping user stories to tasks with skill assignments, effort estimates, and p...

Implement PRDs/specs with a mandatory precheck review before coding. Use when a user asks to implement a PRD/feature spe...

Automatic PRD lifecycle management, organization, and status tracking. Use when working with Product Requirements Docume...

Analyze existing PRD to identify and recommend the single highest-priority task to work on next

This skill supports three modes: Create, Update, and Find.

Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document",...

Fast PRD reference - Quick lookup for product requirements. Auto-activates on "PRD", "产品需求", "读取需求", "read PRD", "查看 PRD...

Reviews and validates Product Requirements Documents for completeness, clarity, and feasibility. Identifies gaps, ambigu...

Start working on a PRD implementation

PRD, 기획서, 요구사항, 제품 기획, MVP, 제품 전략 - Use when brainstorming product ideas, creating PRD documents, defining MVP scope, or...

Convert a Beads PRD markdown file to executable JSON tasks for autonomous execution. Use after writing `.beads/artifacts...

Provides PRD format rules, story sizing guidance, quality gates, and templates for generating ralph-tui compatible prd.j...

Smart PRD generation system that detects existing PRDs and offers flexible workflows. Primarily generates comprehensive,...

Master PRD templates including problem statements, success metrics, requirements, user stories, and technical considerat...

Transform PRDs (Product Requirements Documents) into structured XML app specifications optimized for AI coding agents. C...

Generates production-grade TaskMaster tasks.json from Product Requirements Documents (PRD). Activates via codeword [ACTI...

PRD(요구사항)를 분석하여 테스트 케이스를 도출합니다. TDD의 시작점으로, 구현 전에 테스트 시나리오를 정의합니다. Inside-Out TDD 접근법 적용.

Fast PRD updates - Quick version and feature status updates. Auto-activates on "更新 PRD", "update PRD", "PRD 版本", "完成功能"...

Update PRD based on design decisions and strategic changes made during conversations

Update PRD progress based on git commits and code changes, enhanced by conversation context

Select and validate pricing model for PRD v0.3 Commercial Model. Triggers on requests to set pricing, choose monetizatio...

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers...

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5...

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review...

Define release criteria, deployment environments, and rollback strategies during PRD v0.8 Deployment & Ops. Triggers on...

Create operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Trigg...

Use when creating or reviewing PRDs - enforces 6-point rubric ensuring PRDs have clear objectives, defined use cases, st...

PRD-driven development workflow for feature implementation. Auto-activates on "PRD", "產品需求", "功能文檔", "規格書", "feature spe...

Write comprehensive Product Requirements Documents (PRDs)

Imagine failure first to surface guardrails and feature mitigations.

Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality,...

Configure pre commit hook setup operations. Auto-activating skill for DevOps Basics. Triggers on: pre commit hook setup,...

MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering rep...

ADVISORY validation of code against design principles that linters cannot enforce. Use after linter passes and tests pas...

Rules for using pre-configured APIs in the project, using them only if they are required by the project.

Validates that code changes are ready for server deployment. Use before pushing significant changes to production server...

Gate 4: API contracts document - defines component interfaces and data contractsbefore protocol/technology selection. La...

Gate 5: Data structures document - defines entities, relationships, and ownershipbefore database technology selection. L...

Gate 6: Technology choices document - explicit, versioned, validated technologyselections with justifications. Large Tra...

Gate 2: Feature relationship map - visualizes feature landscape, groupings,and interactions at business level before tec...

Gate 1: Business requirements document - defines WHAT/WHY before HOW.Creates PRD with problem definition, user stories,...

Gate 0 research phase for pre-dev workflow. Dispatches 3 parallel research agentsto gather codebase patterns, external b...

Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks withcomplete code, exact commands, TDD pattern. L...

Gate 7: Implementation tasks - value-driven decomposition into working incrementsthat deliver measurable user value.

Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnosticpatterns before concrete implementat...

修復前強制評估系統. Use for: (1) 測試失敗自動評估, (2) 編譯錯誤分類處理, (3) 強制 Ticket 開設流程