菜单
Create and manage product documentation including PRDs, user stories, and feature specifications. Use when asked to write a PRD, define requirements, create user stories, analyze features, or update product vision. Should ask for clarification and interview the user about product decisions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Audit the codebase for dead code, duplicate code, inefficient code, overloaded code, missing test coverage, non-conforming code, stale documentation, and other best practice violations. Uses parallel subagents for discovery and hands off findings to /architect to create a TDD for fixes.
Review code for quality, standards compliance, and best practices. Use when asked to review code, check for issues, audit code quality, or validate implementations against project standards.
Design and plan software architecture for new features or refactoring. Use when asked to architect a solution, design a feature, create TDD, plan implementation, or make architectural decisions.
Implement code from a TDD (Technical Design Document). Use when asked to build a feature from a TDD, implement a design, or code from a specification. Follows the TDD precisely, implements in phases, and submits for code review.
Debug and fix broken code. Use when errors occur, tests fail, or the application isn't working as expected. Performs root cause analysis, implements fixes, adds regression tests, and documents the bug.
Commit and push changes across all repos in the monorepo. Detects which repos have changes, stages them, generates conventional commit messages, and pushes. Handles root repo and sub-repos (cimplur-core, fyli-fe-v2, fyli-html, fyli-infra) independently.
| name | product-manager |
| description | Create and manage product documentation including PRDs, user stories, and feature specifications. Use when asked to write a PRD, define requirements, create user stories, analyze features, or update product vision. Should ask for clarification and interview the user about product decisions. |
| allowed-tools | Read, Grep, Glob, Task, Write, Edit |
Create product documentation for Cimplur following established patterns and busy professional balancing life and work product vision.
Cimplur helps busy professionals protect and prioritize family time while maintaining work excellence.
DO use:
DON'T use:
Location: /docs/prd/PRD_[FEATURE_NAME].md
Template:
# Product Requirements Document: [Feature Name]
## Overview
[2-3 sentence description of the feature and its purpose]
## Problem Statement
[What problem are we solving? How does this affect the Stretched Parent?]
## Goals
1. [Goal 1 - tied to family-work balance]
2. [Goal 2]
3. [Goal 3]
## User Stories
### [Category 1]
1. As a user, I want [action] so that [family-focused benefit]
2. As a user, I want [action] so that [benefit]
### [Category 2]
3. As a user, I want [action] so that [benefit]
## Feature Requirements
### 1. [Requirement Area]
#### 1.1 [Specific Requirement]
- [Detail]
- [Detail]
#### 1.2 [Specific Requirement]
- [Detail]
### 2. [Requirement Area]
[Continue pattern...]
## Data Model
### [Model Name]
ModelName { field: type field: type }
## UI/UX Requirements
### [Section] Display
- [Requirement]
- [Requirement]
### [Section] Interactions
- [Requirement]
## Technical Considerations
### [Area]
- [Consideration]
## Success Metrics
| Metric | Definition | Target |
|--------|------------|--------|
| [Name] | [How measured] | [Target value] |
## Out of Scope (Future Considerations)
- [Item 1]
- [Item 2]
## Implementation Phases
### Phase 1: [Name]
- [Deliverable]
- [Deliverable]
### Phase 2: [Name]
- [Deliverable]
## Open Questions
1. [Question needing stakeholder input]
2. [Question]
---
*Document Version: 1.0*
*Created: [Date]*
*Status: Draft*
Format:
As a [user type], I want [action/capability] so that [family-focused benefit]
Acceptance Criteria Format:
Given [context]
When [action]
Then [expected outcome]
Example:
User Story: Family Event Protection
As a busy parent, I want to automatically protect family events on my calendar
so that work meetings don't get scheduled over my kids' activities.
Acceptance Criteria:
- Given I have a calendar event with my child's name in the title
- When the system analyzes my calendar
- Then the event is automatically flagged as "Family - Protected"
- Given a protected family event exists
- When someone tries to schedule a meeting at that time
- Then I receive a warning about the conflict
For smaller features or enhancements:
# Feature Spec: [Feature Name]
## Summary
[One paragraph description]
## User Benefit
[How this helps the Stretched Parent]
## Requirements
1. [Requirement]
2. [Requirement]
## Acceptance Criteria
- [ ] [Criterion]
- [ ] [Criterion]
## Dependencies
- [Dependency if any]
## Notes
- [Implementation notes]
/docs/prd/PRODUCT_VISION_2026.md for strategic alignment/docs/prd/ for patterns and related features/docs/tdd/ for technical constraintsReference these when writing PRDs:
When writing technical requirements, consider:
Backend: C#, .NET, PostgreSQL Frontend: Vue.js 3, TypeScript, Pinia, Composition API Architecture: 3-tier (Controllers → Services → Repositories)
Busy parents often miss important family events because work meetings
get scheduled during kids' activities. A parent might have "Emma's
soccer game" on their personal calendar, but their work calendar shows
"available" at that time, leading to meeting conflicts they discover
too late to resolve gracefully.
As a working parent, I want the system to detect when a calendar event
involves my family so that I can protect that time from work conflicts
and be present for moments that matter.
| Metric | Definition | Target |
|--------|------------|--------|
| Family Events Protected | % of detected family events where no work conflict occurred | >95% |
| Presence Score | User self-reported "I was present with family this week" rating | 4+ out of 5 |
/docs/prd/PRD_[FEATURE_NAME].md/docs/prd/PRODUCT_VISION_2026.md/docs/prd/SPEC_[FEATURE_NAME].md