prd
서비스 개발을 위한 제품 요구사항 정의서(PRD)를 작성합니다. 사용자와의 Q&A를 통해 비즈니스 목표, 기능 요구사항, 기술 스택을 정의합니다.
发现 devops sales marketing 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
서비스 개발을 위한 제품 요구사항 정의서(PRD)를 작성합니다. 사용자와의 Q&A를 통해 비즈니스 목표, 기능 요구사항, 기술 스택을 정의합니다.
Organizing features and complex work into manageable/logical tasks
Generates PRDs with user stories and acceptance criteria. Triggers on: create prd, plan feature, write requirements, spec out, requirements for.
Orchestrates the complete lifecycle of a new software project. Use this skill to initiate a new project from a vague idea, guiding it through architectural brainstorming, component definition, and detailed PRD...
Workflow. Apply for task analysis and completion reporting.
Expert in documentation structure, audience targeting, and information architecture. Covers technical docs for Software, Hardware, Robotics, and Data Science.
Turns a single product idea (within this repo) into an evolving requirements collection. Use when the user wants to capture product design, add or refine requirements, or review the current product design state...
flesh out our plan by filling in gaps and clearly building out the specfification
Perform spec-driven development by creating requirements, design, and implementation plan documents. Use when the user wants to follow a structured development approach with separate requirement, design, and pl...
GA4 event tracking patterns and taxonomy. Use when: implementing analytics, tracking user events, e-commerce tracking. Do not use for: general performance optimization (use performance-patterns skill). Workflow...
UX design principles and diagnostic frameworks. Use when: app feels uncomfortable, designing user journeys, layout decisions, product planning. Do not use for: visual styling, color choices, component implement...
ヒアリング結果から非エンジニア向け確認資料を生成するスキル。 ヒアリング完了後、承認を得るために使用。 技術用語を排除し、What/Whyを明確にした資料を作成する。
非エンジニアから要件をヒアリングするスキル。 「アプリを作りたい」「ツールが欲しい」などの発言時に使用。 What(何を作るか)とWhy(なぜ作るか)を明確にすることに集中する。
Document completed development phases in IMPROVEMENTS.md with comprehensive summaries, lessons learned, patterns discovered, and Follow-up status. Ensures session work is captured for future reference and self-...
Design System & UI Kit Development with Figma 2025, Design Tokens, and Component Documentation
Core UI/UX Foundation - Enterprise design systems, component architecture, accessibility, icons, and theming integration
Write or update phase summary documentation. Use when asked to create, write, or update a phase summary, document a phase, or summarize what was built in a phase.
Diagnose requirements problems and guide discovery of real needs and constraints
Transform vague requirements into concrete decisions by exploring the decision space. Use when high-level asks spawn implicit decisions, when defaults need challenging, or when you need systematic discovery of...
Diagnose design problems and guide architecture decisions for solo developers
Manage development phases and quality gates. Use for starting new projects, advancing phases, and navigating the development lifecycle.
QA Interaction Agent. 사용자 인터랙션 테스트 계획 및 Playwright E2E 테스트 작성을 담당합니다. UX/UI 명세 기반의 상세한 테스트 시나리오를 설계합니다.
애니메이션 에이전트. UI 애니메이션과 트랜지션을 설계합니다.
Executive CPO Agent. 제품 전략, 로드맵, 사용자 가치를 담당합니다.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。