systematic-planning
Systematic feature planning workflow - use when starting complex features requiring structured approach
Systematic feature planning workflow - use when starting complex features requiring structured approach
Use when planning feature implementations, creating design artifacts, or structuring development tasks. Apply when user mentions planning, designing, architecting new features, or needs to break down complex features into implementation phases. Use proactively when user describes a substantial new feature to implement.
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의 - You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Break down high-level requirements into concrete implementation plans.
Agentic Scrum Master for software development projects. Use this skill when acting as Scrum Master to facilitate Sprint ceremonies (planning, daily scrum, review, retrospective, backlog refinement), manage Scrum artifacts (product backlog, sprint backlog, user stories, tasks), orchestrate developer sub-agents (frontend, backend, full-stack), and track sprint progress. Triggers include sprint planning, daily standup, backlog grooming, sprint review, retrospective, user story creation, task assignment, and sprint initialization.
Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user story", "create story", "add story" - User mentions "user story", "backlog item", "story" - Running /pm.plan and need to break PRD into implementable stories - Creating backlog items for development team - Need to formalize a requirement into standard story format - Converting feature request into actionable story with acceptance criteria Output: ALWAYS write story files to docs/reference/pm/stories/{story-name}.md
Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user story", "create story", "add story" - User mentions "user story", "backlog item", "story" - Running /pm.plan and need to break PRD into implementable stories - Creating backlog items for development team - Need to formalize a requirement into standard story format - Converting feature request into actionable story with acceptance criteria Output: ALWAYS write story files to docs/reference/pm/stories/{story-name}.md
Write high-quality implementation plans that break down complex work into clear, actionable steps with identified risks and dependencies. Use when breaking down feature specs, planning refactoring or migration efforts, coordinating work across components, identifying technical risks, or creating roadmaps for complex changes. Triggers include "implementation plan", "write plan", "plan feature", "break down work", "technical planning", or when transforming requirements into concrete implementation steps.
Create detailed implementation plans. Use when planning new features or refactoring work.
Comprehensive BOQ (Bill of Quantities) creation and management for construction projects. This skill should be used when Claude needs to: (1) Create new BOQ files with standard work categories, (2) Add items to existing BOQ, (3) Manage construction cost estimates with material and labor breakdowns, (4) Generate Thai construction project cost sheets with proper formatting
Draft outcome-oriented OKRs with leading indicators and initiatives tied to the product strategy.
ユーザー要件を分析し、システム設計ドキュメント(DESIGN.md)を生成します。ユーザー要件が曖昧または不明確な場合、システムアーキテクチャの設計が必要な場合、大規模な機能開発の設計仕様が必要な場合、技術的実現可能性の検証が必要な場合に使用します。不明点はAskUserQuestionツールで確認します。
Facilitate structured brainstorming sessions using proven frameworks for ideation and problem-solving
Generate standalone user stories for features without creating a full PRD. Perfect for backlog grooming and story refinement.
Use when (1) breaking down a feature request into implementable tasks, (2) creating a detailed feature specification, (3) preparing work for development. Generates feature plans with acceptance criteria and task breakdown.
Front-end planning and breakdowns for UI tasks; use when asked to plan, estimate, or outline steps for building front-end features (e.g., build/create/implement/plan a UI).
Enables Masterbuilder to conduct UX testing using artisans as user personas. After implementation, artisans embody different user types to verify the work from real-world perspectives.
Эксперт Customer Journey. Используй для mapping touchpoints, user experience и journey optimization.