product

プロダクトマネジメント総合ガイド（基礎・AIプロダクト・A/Bテスト・成長戦略・GPM・PLG・カスタマーサクセス・Claude Code PM活用）。 Use when practicing product management, managing AI products, designing experiments, growth product management, PLG strategy, customer success, writing PRDs/requirements docs, prioritizing roadmaps, or using Claude Code as PM tool. AARRR海賊指標、AIプロダクトライフサイクル、MLプロダクト化、AI統合戦略、オンライン実験設計、PM調査パターン、GPM実践、リテンション戦略、拡張収益、優先順位付け手法、ロードマップ（Now-Next-Later）、要件定義（PRD）、責任あるAIを含む。 For engineer-focused user story writing techniques (templates, common mistakes, splitting), use writing-user-stories instead. For writing use cases as detailed behavioral requirements, use writing-use-cases instead.

Guides writing use cases as behavioral requirements: the stakeholder-contract model, goal levels (summary/user-goal/subfunction), functional and design scope (in/out and actor-goal lists, briefs), stakeholders and interests, actors versus job-title roles, preconditions and minimal/success guarantees and triggers, the main success scenario with action-step guidelines, extension conditions and handling, sub and extension use cases, eight write-up formats and per-project templates, the 12-step writing recipe, review reminders, pass/fail quality tests, common mistakes, and expansion into design, UI, and tests. Use when writing or reviewing use cases, specifying system behavior in detail, or choosing a detail level. For lightweight agile story cards, acceptance criteria, and splitting, use writing-user-stories instead. For PRDs, roadmaps, and prioritization, use practicing-product-management instead. For the Use Cases layer of Clean Architecture and DDD modeling, use devkit:applying-clean-architecture instead.

Guides effective user story creation for software projects covering story templates (As a.../I want.../So that...), common mistakes, technical requirements to story conversion, acceptance criteria writing, and story splitting techniques. Use when writing user stories, converting technical requirements to stories, or improving backlog quality. For product management practices (PRD, roadmap, prioritization), use practicing-product-management instead. For detailed behavioral requirements with stakeholder interests, goal levels, main success scenarios, and extension handling, use writing-use-cases instead.