AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
中文简介正在准备中。当前显示原文说明。
ilandahan/AID102026年9月23日 更新
免费在 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（原文）
安装前可以查看交给 AI 代理的指令内容。
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
| Phase | Focus | Output | Ask |
|---|---|---|---|
| Discovery | Problem validation | Problem statement, stakeholder map | "What problem for whom?" / "Who touches this?" / "What does success look like?" / "Cost of not solving?" |
| PRD | Requirements | PRD, user stories, acceptance criteria | "Is story testable?" / "Criteria specific?" / "What's out of scope?" / "Dependencies?" |
| Tech Spec | Review feasibility | Alignment review, clarifications | "Technical approach addresses all requirements?" / "Requirements technically problematic?" / "Trade-offs?" |
| Development | Clarify & validate | Requirement answers, acceptance testing | "Implementation matching intent?" / "Need to adjust scope?" |
| QA & Ship | Acceptance | Sign-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-Pattern | Fix |
|---|---|
| Solution-first | Start with problem |
| Implementation in requirements | Focus on WHAT not HOW |
| Assuming stakeholders | Verify who's affected |
| Vague criteria | "It should be fast" -> "<2s" |
| Scope creep | Explicit 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
| Role | How |
|---|---|
| Developers | Clear requirements, answer questions |
| QA | Review scenarios, clarify edge cases |
| Tech Leads | Discuss 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 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日 更新