67f3922e4f
Phase 1 — Agent & Command Foundation: - Rewrite cs-project-manager agent (55→515 lines, 4 workflows, 6 skill integrations) - Expand cs-product-manager agent (408→684 lines, orchestrates all 8 product skills) - Add 7 slash commands: /rice, /okr, /persona, /user-story, /sprint-health, /project-health, /retro Phase 2 — Script Gap Closure (2,779 lines): - jira-expert: jql_query_builder.py (22 patterns), workflow_validator.py - confluence-expert: space_structure_generator.py, content_audit_analyzer.py - atlassian-admin: permission_audit_tool.py - atlassian-templates: template_scaffolder.py (Confluence XHTML generation) Phase 3 — Reference & Asset Enrichment: - 9 product references (competitive-teardown, landing-page-generator, saas-scaffolder) - 6 PM references (confluence-expert, atlassian-admin, atlassian-templates) - 7 product assets (templates for PRD, RICE, sprint, stories, OKR, research, design system) - 1 PM asset (permission_scheme_template.json) Phase 4 — New Agents: - cs-agile-product-owner, cs-product-strategist, cs-ux-researcher Phase 5 — Integration & Polish: - Related Skills cross-references in 8 SKILL.md files - Updated product-team/CLAUDE.md (5→8 skills, 6→9 tools, 4 agents, 5 commands) - Updated project-management/CLAUDE.md (0→12 scripts, 3 commands) - Regenerated docs site (177 pages), updated homepage and getting-started Quality audit: 31 files reviewed, 29 PASS, 2 fixed (copy-frameworks.md, governance-framework.md) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
133 lines
3.3 KiB
Markdown
133 lines
3.3 KiB
Markdown
# Product Requirements Document (PRD)
|
|
|
|
## Document Info
|
|
|
|
| Field | Value |
|
|
|-------|-------|
|
|
| **Author** | [Your Name] |
|
|
| **Status** | Draft / In Review / Approved |
|
|
| **Created** | YYYY-MM-DD |
|
|
| **Last Updated** | YYYY-MM-DD |
|
|
| **Reviewers** | [Names] |
|
|
| **Target Release** | [Quarter or Date] |
|
|
|
|
---
|
|
|
|
## Problem Statement
|
|
|
|
### What problem are we solving?
|
|
[Describe the user problem in 2-3 sentences. Focus on the pain, not the solution.]
|
|
|
|
### Who is affected?
|
|
[Identify the user segment(s) experiencing this problem.]
|
|
|
|
### How do we know this is a problem?
|
|
[Link to evidence: interview insights, support tickets, analytics data, churn analysis.]
|
|
|
|
### What happens if we do nothing?
|
|
[Quantify the cost of inaction: lost revenue, churn risk, competitive disadvantage.]
|
|
|
|
---
|
|
|
|
## User Stories
|
|
|
|
| # | As a... | I want to... | So that... | Priority |
|
|
|---|---------|-------------|-----------|----------|
|
|
| 1 | [role] | [capability] | [benefit] | Must Have |
|
|
| 2 | [role] | [capability] | [benefit] | Should Have |
|
|
| 3 | [role] | [capability] | [benefit] | Nice to Have |
|
|
|
|
---
|
|
|
|
## Solution Overview
|
|
|
|
### Proposed Solution
|
|
[High-level description of what we will build. 3-5 sentences.]
|
|
|
|
### Key User Flows
|
|
[Describe the primary user interactions. Include wireframes or mockups if available.]
|
|
|
|
1. **Flow 1:** [Description]
|
|
2. **Flow 2:** [Description]
|
|
3. **Flow 3:** [Description]
|
|
|
|
### How It Works
|
|
[Explain the mechanism or approach. Include technical considerations if relevant.]
|
|
|
|
---
|
|
|
|
## Success Metrics
|
|
|
|
| Metric | Current | Target | Timeframe |
|
|
|--------|---------|--------|-----------|
|
|
| [Primary metric] | [Baseline] | [Goal] | [When] |
|
|
| [Secondary metric] | [Baseline] | [Goal] | [When] |
|
|
| [Guardrail metric] | [Baseline] | [Must not worsen] | [When] |
|
|
|
|
### How We Will Measure
|
|
[Describe tracking approach: analytics events, surveys, A/B test design.]
|
|
|
|
---
|
|
|
|
## Technical Requirements
|
|
|
|
### System Requirements
|
|
- [Requirement 1: e.g., API response time < 200ms]
|
|
- [Requirement 2: e.g., Support 10K concurrent users]
|
|
- [Requirement 3: e.g., Mobile responsive]
|
|
|
|
### Dependencies
|
|
- [Dependency 1: e.g., Payment service API update]
|
|
- [Dependency 2: e.g., Design system component]
|
|
|
|
### Security & Privacy
|
|
- [Data handling requirements]
|
|
- [Authentication/authorization needs]
|
|
- [Compliance considerations]
|
|
|
|
---
|
|
|
|
## Timeline
|
|
|
|
| Phase | Dates | Deliverables |
|
|
|-------|-------|-------------|
|
|
| Design | [Start - End] | Wireframes, user flows, design specs |
|
|
| Development | [Start - End] | Feature implementation, unit tests |
|
|
| QA | [Start - End] | Test plan execution, bug fixes |
|
|
| Beta | [Start - End] | Limited rollout, feedback collection |
|
|
| GA | [Date] | Full release, documentation, training |
|
|
|
|
---
|
|
|
|
## Risks
|
|
|
|
| Risk | Likelihood | Impact | Mitigation |
|
|
|------|-----------|--------|-----------|
|
|
| [Risk 1] | High/Med/Low | High/Med/Low | [Plan] |
|
|
| [Risk 2] | High/Med/Low | High/Med/Low | [Plan] |
|
|
|
|
---
|
|
|
|
## Out of Scope
|
|
|
|
The following items are explicitly NOT included in this release:
|
|
- [Item 1: brief explanation of why]
|
|
- [Item 2: brief explanation of why]
|
|
- [Item 3: brief explanation of why]
|
|
|
|
---
|
|
|
|
## Decision Log
|
|
|
|
| # | Decision | Date | Decided By | Rationale |
|
|
|---|----------|------|-----------|-----------|
|
|
| 1 | [Decision] | [Date] | [Name] | [Why] |
|
|
|
|
---
|
|
|
|
## Change History
|
|
|
|
| Version | Date | Author | Changes |
|
|
|---------|------|--------|---------|
|
|
| 0.1 | [Date] | [Name] | Initial draft |
|