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(원문)
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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일 업데이트