AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
日本語の概要は準備中です。原文の説明を表示しています。
PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Depth: references/prd-writing-guide.md, references/metrics-definition-guide.md, references/stakeholder-management.md.
| 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?" |
As a [role]
I want [capability]
So that [benefit]
Acceptance Criteria:
- Given [context], when [action], then [outcome]
| 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 |
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
| Role | How |
|---|---|
| Developers | Clear requirements, answer questions |
| QA | Review scenarios, clarify edge cases |
| Tech Leads | Discuss feasibility, accept constraints |
Quantify. Bad: "Make dashboard faster". Good: "Reduce load from 4s to <1s (P95)".
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
日本語の概要は準備中です。原文の説明を表示しています。