Loading...
Loading...
Found 12 Skills
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.
Project management and product requirement analysis. Use this skill when you need to create project plans, write PRD documents, manage tasks, or conduct requirement analysis.
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Creates structured plans from requirements. Generates comprehensive plans with steps, dependencies, risks, and success criteria. Coordinates with specialist agents for planning input and validates plan completeness.
Analyze requirements during the functional design and problem diagnosis stages to develop executable solutions, and output user-facing and AI-facing action documents separately.
A documentation-focused skill for game architecture design. Produces technical selection, design, and planning documents through a structured pipeline. Use this skill to generate requirement analysis, technical design, and implementation planning documents for new game projects or major feature development.
Analyze development requirements and define acceptance criteria for AEM Edge Delivery Services tasks. Handles new blocks, variants, modifications, bug fixes, and styling changes with task-specific guidance.
신규 기능 요구사항을 대화형으로 수집하여 AI 최적화 Spec + DB 스키마 기본 설계를 생성하는 스킬. "Spec 만들어줘", "신규 기능 기획", "요구사항 정리" 키워드로 트리거. 기존 기능 분석이 필요하면 peach-gen-feature-docs를 사용한다.
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.
Use when you need to move a feature from a vague concept to an executable development plan, and complete requirement analysis, task breakdown, and status tracking within the same plan document.
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Triggers on /brainstorm command, when exploring ideas before planning, when user describes a vague goal or feature request, or when design decisions need collaborative exploration. Explores user intent, requirements and design before implementation.
Generate implementable architecture solutions based on business requirements and tech stacks, providing structured suggestions and tech stack selection optimization through a four-step process (information collection, requirement sorting, iterative improvement, solution output)