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>
1.2 KiB
1.2 KiB
User Story
Story Info
| Field | Value |
|---|---|
| Title | [Short descriptive title] |
| Epic | [Parent epic name/link] |
| Story Points | [Estimate] |
| Priority | Must Have / Should Have / Nice to Have |
| Assignee | [Name] |
| Sprint | [Sprint number] |
User Story
As a [type of user/role],
I want [capability or feature],
So that [benefit or value I receive].
Acceptance Criteria
Scenario 1: [Happy Path]
- Given [precondition or context]
- When [action the user takes]
- Then [expected outcome]
Scenario 2: [Alternative Path]
- Given [precondition or context]
- When [action the user takes]
- Then [expected outcome]
Scenario 3: [Edge Case / Error]
- Given [precondition or context]
- When [action the user takes]
- Then [expected error handling or outcome]
Notes
- [Technical notes, design references, API details]
- [Dependencies on other stories or external systems]
- [Out of scope items for this story]
- [Links to mockups, prototypes, or design files]
Definition of Done
- Acceptance criteria met
- Code reviewed and approved
- Tests written and passing
- Documentation updated
- Product Owner accepted