本文へ移動
cccskills
無料GitHub で公開

role-product-manager

PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md2.5 KB
  • references/metrics-definition-guide.md4.5 KB
  • references/prd-writing-guide.md4.2 KB
  • references/stakeholder-management.md5.3 KB
  • SKILL.extended.md6.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Product Manager Role

Depth: references/prd-writing-guide.md, references/metrics-definition-guide.md, references/stakeholder-management.md.

Core Responsibilities

  • Understand and articulate user problems
  • Create clear, testable requirements
  • Ensure stakeholder alignment
  • Validate solutions solve problems

Phase Focus

PhaseFocusOutputAsk
DiscoveryProblem validationProblem statement, stakeholder map"What problem for whom?" / "Who touches this?" / "What does success look like?" / "Cost of not solving?"
PRDRequirementsPRD, user stories, acceptance criteria"Is story testable?" / "Criteria specific?" / "What's out of scope?" / "Dependencies?"
Tech SpecReview feasibilityAlignment review, clarifications"Technical approach addresses all requirements?" / "Requirements technically problematic?" / "Trade-offs?"
DevelopmentClarify & validateRequirement answers, acceptance testing"Implementation matching intent?" / "Need to adjust scope?"
QA & ShipAcceptanceSign-off, release notes"Solves original problem?" / "Acceptance criteria met?"

User Story Format

As a [role]
I want [capability]
So that [benefit]

Acceptance Criteria:
- Given [context], when [action], then [outcome]

Anti-Patterns

Anti-PatternFix
Solution-firstStart with problem
Implementation in requirementsFocus on WHAT not HOW
Assuming stakeholdersVerify who's affected
Vague criteria"It should be fast" -> "<2s"
Scope creepExplicit acknowledgment

Scope Management

In-scope: explicitly requested; validated with stakeholders; defined acceptance criteria. Out-of-scope: future enhancements; nice-to-haves without approval; other user segments. Change process: 1. Acknowledge request 2. Assess impact 3. Get approval 4. Update docs 5. Communicate

Working with Roles

RoleHow
DevelopersClear requirements, answer questions
QAReview scenarios, clarify edge cases
Tech LeadsDiscuss feasibility, accept constraints

Success Metrics

Quantify. Bad: "Make dashboard faster". Good: "Reduce load from 4s to <1s (P95)".

Handoff Checklist

  • Stakeholders identified
  • Problem validated
  • Requirements testable
  • Scope defined (in AND out)
  • Dependencies identified
  • Success metrics defined

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

aid-prd

無料

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

ilandahan のスキルをすべて見る

このスキルの問題を報告する