fix-planner
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
Product management expertise for story creation, backlog management, validation, and release coordination
Facilitate ideation sessions to explore options. Use when exploring solutions before committing to a direction.
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md
Structured iOS UX/UI review checklist. Use to critique hierarchy, spacing, affordances, copy, and states and output prioritized fixes (platform guidance, not implementation).
Expert knowledge for running winter festival operations (Security, Marketing, CX, Lost & Found).
Creates Features following the T-Minus-15 process template. Features represent significant deliverables that contain multiple User Stories. Includes proper metadata, MoSCoW prioritization, effort estimates, deliverables, and benefit hypothesis.
Quality assurance standards and AI collaboration principles for career_ios_backend. Automatically invoked when discussing code quality, standards, refactoring, or optimization. Trigger keywords: "quality", "refactor", "optimize", "best practices", "code review", "品質", "重構", "優化", "最佳實踐" Defines what's required vs. optional in prototype phase, and when to upgrade standards.
Calculate Use Case Points (UCP) for software development work using Onshore's v4.0 complete coverage methodology. Includes work item classification (stories/tasks/bugs/tests), transaction counting, Technical Complexity Factor (TCF) calculation, Environmental Complexity Factor (ECF) calculation, Specificity Adjustment Factor (SAF) scoring, and comprehensive reporting. Use when analyzing development effort, estimating projects, calculating billing, generating UCP reports, analyzing Azure DevOps work items, analyzing git repositories, counting use case transactions, or any UCP-related calculation.
Use this skill to break down requirements into user stories, acceptance criteria, and actionable tasks. Invoke when starting a new feature or receiving new requirements.
This skill should be used when estimating development time for Jira tickets. It provides both manual and AI-assisted estimates with T-shirt sizes, story points, and phase-by-phase time breakdowns based on task type classification, complexity scoring, and project architecture (monolithic/serverless/frontend/fullstack/mobile/test_automation).
Review specifications for completeness, clarity, and unambiguous requirements.
対話形式で要件を深掘りし、実装者が迷わない詳細な仕様書を作成します。ユーザーが気づいていない課題や考慮漏れを質問で洗い出し、UI/UXを含む包括的な仕様を文書化します。
Draft detailed engineering specs from an approved PRD. Use when generating or updating the engineering specification for a feature, before implementation begins.
WCAG 2.1/2.2準拠のアクセシビリティ監査と改善を支援します。Webサイトやアプリケーションのアクセシビリティ問題を特定し、優先度付きの改善提案を提供します。アクセシビリティチェック、WCAG準拠確認、スクリーンリーダーテストが必要な場合に使用してください。
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.
Use when designing interactions, workflows, or interfaces where user focus matters. Covers protecting flow state, reducing interruptions, and creating immersive experiences.
Build WCAG 2.1 AA compliant web applications for University of Sheffield. Covers semantic HTML, ARIA patterns, form accessibility, keyboard navigation, color contrast, alt text, captions, and automated testing. Use when creating websites, web apps, forms, interactive components, or auditing accessibility for WCAG compliance, screen readers, keyboard access, or inclusive design.
Эксперт ABM. Используй для account-based marketing, target account selection и personalized campaigns.
A/Bテストと実験の設計・追跡を支援します。仮説検証、統計分析、メトリクス定義を提供します。データドリブンな意思決定、実験的機能の検証が必要な場合に使用してください。
Conducts comprehensive 90-minute discovery interviews to extract complete product requirements before implementation. Triggers when starting new SaaS projects, defining product scope, or validating ideas. Includes product management expertise to guide users through difficult questions.