[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3C665RHV7J6YKYAAFGTKX":3,"skill-same:01M6D3C665RHV7J6YKYAAFGTKX":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6D3C665RHV7J6YKYAAFGTKX","product-brief",null,"Extract product ideas through guided questions and generate PRD","hemory\u002Famp-legacy-do-not-use","hemory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21179881?v=4","01M6D31HFJ391DN8N0JP8AQGFE","Hemory Phifer","01M6D31HKXVTEN27AT6R4PP2ZJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproduct-brief\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30],"product","brief","product brief","generate","prd","extract","ideas","2026-11-10 10:12:30",false,"---\nname: product-brief\ndescription: Extract product ideas through guided questions and generate PRD\n---\n\n## Purpose\n\nExtract product ideas from your head through guided questioning, then generate a detailed Product Requirements Document (PRD). Designed for product people who have a vision but need help articulating it clearly.\n\n## The Problem This Solves\n\nYou have an idea for a product or feature in your mind, but struggle to explain it comprehensively. This command acts as your product thought partner — asking the right questions to extract what you're envisioning, then structuring it into a PRD ready for a team to execute.\n\n## Usage\n\n```\n\u002Fproduct-brief [initial idea]\n```\n\n**Examples:**\n- `\u002Fproduct-brief Add a notification system to our app`\n- `\u002Fproduct-brief Build a customer feedback portal`\n- `\u002Fproduct-brief Create an onboarding flow for new users`\n- `\u002Fproduct-brief` (prompts you for the idea)\n\n---\n\n## Process Flow\n\n### Phase 1: Capture Initial Idea\n\n**If no idea is provided:**\nAsk: \"What product or feature are you thinking about?\"\n- Wait for their description (1 sentence to several paragraphs)\n- Capture it as the starting point\n\n**If idea is provided:**\nStart with whatever the user provides:\n- Could be 1 sentence or 5 paragraphs\n- Capture it as the starting point\n- Don't judge, just absorb\n\nDisplay:\n\n```markdown\n## Initial Idea\n\n[User's description]\n\n---\n\n**Next:** I'll ask a few questions to understand this better.\n```\n\n---\n\n### Phase 2: Clarifying Questions (Conversational)\n\n**Important:** Ask questions conversationally, not as a survey. 2-3 questions at a time, then wait for answers before asking more.\n\n**Question Strategy:**\n\n**Round 1 (Critical Context):**\n- What problem does this solve?\n- Who is this for?\n- What success looks like?\n\n**Round 2 (Constraints & Scope):**\nBased on Round 1 answers, ask about:\n- Timeline expectations\n- Technical constraints\n- Existing systems to integrate with\n- What's explicitly out of scope\n\n**Round 3 (User Experience):**\n- How do users discover this?\n- What's the core user journey?\n- What actions should be easy vs hard?\n\n**Round 4 (Success & Validation):**\n- How will we know this succeeded?\n- What are we assuming that needs validation?\n- What dependencies exist?\n\n**Adaptive questioning:** If user mentions stakeholders, budget, or other context early, adjust questions accordingly. Don't ask what you already know.\n\nAfter each round, acknowledge answers briefly and transition naturally:\n> \"Got it. That helps me understand [X]. A few more questions about [Y]...\"\n\n---\n\n### Phase 3: Understanding Summary\n\nBefore moving forward, confirm you captured the vision correctly:\n\n```markdown\n## What I Heard\n\n**The Problem:**\n[Synthesized problem statement]\n\n**Target Users:**\n[Who this is for]\n\n**Core Value:**\n[The main benefit\u002Foutcome]\n\n**Key Constraints:**\n[Timeline, technical, scope boundaries]\n\n**Assumptions to Validate:**\n[Things we're assuming but should test]\n\n---\n\n**Does this capture your vision? Type \"yes\" to continue or correct anything above.**\n```\n\nIf user corrects, update and re-confirm.\n\n---\n\n### Phase 4: Spec Doc\n\nUser triggers with: `spec doc` or `create spec`\n\nGenerate structured product spec:\n\n```markdown\n# Product Spec: [Feature\u002FProduct Name]\n\n**Date:** YYYY-MM-DD\n**Owner:** [User's name]\n**Status:** Draft\n\n---\n\n## Executive Summary\n\n[2-3 sentence pitch: what this is and why it matters]\n\n---\n\n## Problem Statement\n\n### Current Situation\n[What exists today]\n\n### Pain Points\n- [Specific pain 1]\n- [Specific pain 2]\n- [Specific pain 3]\n\n### Impact of Inaction\n[What happens if we don't build this]\n\n---\n\n## Target Audience\n\n### Primary Users\n[Who will use this most]\n\n### Secondary Users\n[Who else benefits]\n\n### User Characteristics\n- [Key trait 1]\n- [Key trait 2]\n- [Key trait 3]\n\n---\n\n## Solution Overview\n\n[High-level description of what we're building]\n\n---\n\n## Key Features & Functionality\n\n### Must Have (MVP)\n1. **[Feature 1]**\n   - Description\n   - Why it's critical\n   \n2. **[Feature 2]**\n   - Description\n   - Why it's critical\n\n### Should Have (Phase 2)\n1. **[Feature 3]**\n   - Description\n   - Why it's valuable\n\n### Nice to Have (Future)\n1. **[Feature 4]**\n   - Description\n   - Why it's desirable\n\n---\n\n## Success Metrics\n\n### Primary Metric\n[The one number that matters most]\n\n### Secondary Metrics\n- [Metric 2]\n- [Metric 3]\n\n### Leading Indicators\n[Early signals of success\u002Ffailure]\n\n---\n\n## Assumptions & Risks\n\n### Key Assumptions\n1. [Assumption 1]\n   - How to validate: [Test method]\n   \n2. [Assumption 2]\n   - How to validate: [Test method]\n\n### Risks\n1. **[Risk 1]** — [Mitigation strategy]\n2. **[Risk 2]** — [Mitigation strategy]\n\n---\n\n## Dependencies\n\n### Technical\n- [System\u002FAPI\u002Fservice dependency]\n\n### Team\n- [Who needs to be involved]\n\n### External\n- [Third-party dependencies]\n\n---\n\n## Out of Scope\n\nExplicitly not included:\n- [Thing 1]\n- [Thing 2]\n- [Thing 3]\n\n---\n\n## Open Questions\n\n- [ ] [Question 1]\n- [ ] [Question 2]\n- [ ] [Question 3]\n\n---\n\n**Next Steps:**\n\n- Type `prioritize` to rank features by effort\u002Fimpact\n- Type `design flows` to create detailed user flows\n- Type `create prd` to generate final PRD\n- Type `back` to revise anything above\n```\n\n---\n\n### Phase 5: Prioritization (Optional)\n\nUser triggers with: `prioritize`\n\nCreate effort\u002Fimpact matrix:\n\n```markdown\n## Feature Prioritization\n\n| Feature | Impact | Effort | Priority | Rationale |\n|---------|--------|--------|----------|-----------|\n| [Feature 1] | High | Low | P0 | [Why] |\n| [Feature 2] | High | Medium | P0 | [Why] |\n| [Feature 3] | Medium | Low | P1 | [Why] |\n| [Feature 4] | Low | High | P2 | [Why] |\n\n### Recommended MVP Scope\n\nBased on high impact + reasonable effort:\n1. [Feature 1]\n2. [Feature 2]\n3. [Feature 3]\n\n**Estimated Effort:** [X weeks\u002Fsprints]\n\n---\n\n**Next:**\n- Type `design flows` to create user flows\n- Type `create prd` to generate final PRD\n- Type `back` to revise spec\n```\n\n---\n\n### Phase 6: Design Flows (Optional)\n\nUser triggers with: `design flows`\n\nCreate detailed user flows and screen specs:\n\n```markdown\n## User Flows & Screen Specifications\n\n### Flow 1: [Primary User Journey]\n\n**Entry Point:** [How user arrives]\n\n**Steps:**\n\n#### Step 1: [Screen Name]\n\n**Layout:**\n- [Header elements]\n- [Main content area]\n- [Actions\u002Fbuttons]\n\n**User Actions:**\n- Click [X] → [Outcome]\n- Enter [Y] → [Validation rules]\n- Cancel → [State change]\n\n**Navigation:**\n- Success → [Next screen]\n- Error → [Error state]\n- Back → [Previous screen]\n\n**Validation Rules:**\n- [Field 1]: [Rules]\n- [Field 2]: [Rules]\n\n**States:**\n- Default: [Description]\n- Loading: [What user sees]\n- Error: [Error message]\n- Success: [Confirmation]\n\n---\n\n#### Step 2: [Next Screen]\n\n[Same structure as Step 1]\n\n---\n\n### Flow 2: [Secondary Journey]\n\n[Same structure as Flow 1]\n\n---\n\n**Next:**\n- Type `create prd` to generate final PRD\n- Type `back` to revise flows\n```\n\n---\n\n### Phase 7: Final PRD\n\nUser triggers with: `create prd` or `generate prd`\n\nGenerate comprehensive PRD combining all previous phases:\n\n```markdown\n# Product Requirements Document\n## [Product\u002FFeature Name]\n\n**Author:** [User name]\n**Date:** YYYY-MM-DD\n**Status:** Draft\n**Last Updated:** YYYY-MM-DD\n\n---\n\n## Document Control\n\n| Version | Date | Author | Changes |\n|---------|------|--------|---------|\n| 0.1 | YYYY-MM-DD | [Name] | Initial draft |\n\n---\n\n## Executive Summary\n\n[2-3 paragraphs covering: what, why, who, success]\n\n---\n\n## Background & Context\n\n### Current State\n[What exists today]\n\n### Problem Statement\n[The problem we're solving]\n\n### Opportunity\n[Why now, why us]\n\n---\n\n## Goals & Success Metrics\n\n### Primary Objective\n[The main goal]\n\n### Success Metrics\n\n**Primary:**\n- [Metric 1]: [Target]\n\n**Secondary:**\n- [Metric 2]: [Target]\n- [Metric 3]: [Target]\n\n**Leading Indicators:**\n- [Early signal 1]\n- [Early signal 2]\n\n---\n\n## Target Users\n\n### Primary Audience\n[Detailed description]\n\n### Use Cases\n1. **[Use Case 1]**\n   - As a [user type]\n   - I want to [action]\n   - So that [benefit]\n\n2. **[Use Case 2]**\n   - As a [user type]\n   - I want to [action]\n   - So that [benefit]\n\n---\n\n## Solution Overview\n\n[Comprehensive description of what we're building]\n\n---\n\n## Functional Requirements\n\n### Must Have (P0)\n\n#### Requirement 1: [Name]\n- **Description:** [What it does]\n- **Acceptance Criteria:**\n  - [ ] [Criterion 1]\n  - [ ] [Criterion 2]\n  - [ ] [Criterion 3]\n- **User Story:** As a [X], I want [Y], so that [Z]\n\n#### Requirement 2: [Name]\n[Same structure]\n\n### Should Have (P1)\n\n[Same structure as Must Have]\n\n### Nice to Have (P2)\n\n[Same structure as Must Have]\n\n---\n\n## User Experience\n\n### User Flows\n[Reference to flows from Phase 6, or create if skipped]\n\n### Key Screens\n[High-level screen descriptions]\n\n### Interaction Patterns\n[How users interact with the feature]\n\n---\n\n## Technical Requirements\n\n### Performance\n- [Requirement 1]\n- [Requirement 2]\n\n### Security\n- [Requirement 1]\n- [Requirement 2]\n\n### Integration Points\n- [System 1]: [What needs to connect]\n- [System 2]: [What needs to connect]\n\n### Data Requirements\n- [What data is collected]\n- [Where it's stored]\n- [How it's used]\n\n---\n\n## Design Requirements\n\n### Visual Design\n- [Style guide compliance]\n- [Responsive requirements]\n- [Accessibility standards]\n\n### Content Requirements\n- [Copy needs]\n- [Translation needs]\n- [Asset requirements]\n\n---\n\n## Dependencies & Constraints\n\n### Dependencies\n- **Technical:** [List]\n- **Team:** [Who needs to be involved]\n- **External:** [Third parties]\n\n### Constraints\n- **Timeline:** [Dates\u002Fmilestones]\n- **Budget:** [If applicable]\n- **Technical:** [Platform limitations]\n\n---\n\n## Assumptions & Risks\n\n### Assumptions\n1. [Assumption 1]\n   - **Validation method:** [How to test]\n   - **Impact if wrong:** [Consequence]\n\n2. [Assumption 2]\n   - **Validation method:** [How to test]\n   - **Impact if wrong:** [Consequence]\n\n### Risks\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|------------|--------|------------|\n| [Risk 1] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Strategy] |\n| [Risk 2] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Strategy] |\n\n---\n\n## Out of Scope\n\nExplicitly not included in this version:\n- [Item 1] — [Why\u002Fwhen it might be included]\n- [Item 2] — [Why\u002Fwhen it might be included]\n- [Item 3] — [Why\u002Fwhen it might be included]\n\n---\n\n## Open Questions\n\n- [ ] [Question 1] — Owner: [Name], Due: [Date]\n- [ ] [Question 2] — Owner: [Name], Due: [Date]\n- [ ] [Question 3] — Owner: [Name], Due: [Date]\n\n---\n\n## Timeline & Milestones\n\n| Milestone | Target Date | Status |\n|-----------|-------------|--------|\n| PRD Complete | [Date] | In Progress |\n| Design Complete | [Date] | Not Started |\n| Dev Complete | [Date] | Not Started |\n| QA Complete | [Date] | Not Started |\n| Launch | [Date] | Not Started |\n\n---\n\n## Stakeholders\n\n| Name | Role | Involvement |\n|------|------|-------------|\n| [Name] | [Role] | [What they do] |\n| [Name] | [Role] | [What they do] |\n\n---\n\n## Appendix\n\n### Research\n[Link to user research, competitive analysis, etc.]\n\n### Design Mockups\n[Links to designs when available]\n\n### Technical Specs\n[Links to technical documentation]\n\n---\n\n**Document Status:** Ready for Review\n\n**Next Actions:**\n- [ ] Review with stakeholders\n- [ ] Refine based on feedback\n- [ ] Get approval to proceed\n- [ ] Hand off to design\u002Fengineering\n\n---\n\n*This PRD was generated using the \u002Fproduct-brief command. Update as needed.*\n```\n\n---\n\n### Phase 8: Save & Integration\n\nAfter generating the PRD:\n\n1. **Save the document:**\n   - Create folder: `04-Projects\u002F[Product Name]\u002F`\n   - Save as: `04-Projects\u002F[Product Name]\u002FPRD.md`\n\n2. **Create person pages** (if stakeholders mentioned):\n   - For each stakeholder mentioned, check if person page exists\n   - Create\u002Fupdate pages in `People\u002FInternal\u002F` or `People\u002FExternal\u002F`\n   - Add note in their page referencing this project\n\n3. **Link to 03-Tasks\u002FTasks.md:**\n   - If user mentioned any immediate actions, suggest creating tasks\n   - Link tasks to the project\n\n4. **Confirm completion:**\n\n```markdown\n## ✅ PRD Created\n\n**Saved to:** `04-Projects\u002F[Product Name]\u002FPRD.md`\n\n**Next Steps:**\n1. Review and refine the PRD\n2. Share with stakeholders for feedback\n3. Use `\u002Fproject-health` to track progress\n4. Create tasks in 03-Tasks\u002FTasks.md when ready to execute\n\n**Want to:**\n- Revise any section → Just tell me what to change\n- Create tasks from this PRD → Say \"create tasks\"\n- Share with stakeholders → I can draft an email\n```\n\n---\n\n## Navigation Commands\n\nAt any phase, users can:\n\n- `back` or `previous` — Return to previous phase\n- `skip to prd` — Jump directly to final PRD\n- `revise [section]` — Edit specific section\n- `start over` — Begin from scratch\n- `save` — Save current progress\n\n---\n\n## Conversational Style\n\n- **Be a thought partner, not an interrogator**\n- Ask follow-up questions when answers reveal gaps\n- Challenge assumptions constructively\n- Suggest alternatives when you spot potential issues\n- Keep momentum — don't let the process feel like homework\n\n**Good:**\n> \"Interesting. If this is for enterprise customers, how do we handle single sign-on? Or is that something we're punting to Phase 2?\"\n\n**Bad:**\n> \"Question 7: Please describe your authentication strategy.\"\n\n---\n\n## Tips for Effectiveness\n\n### For the User\n- Start with whatever you have — even 1 sentence is enough\n- Don't worry about being comprehensive upfront\n- The questions will extract what's in your head\n- You can always revise and refine\n\n### For Amp\n- Listen for what's NOT being said\n- If scope sounds too big, flag it early\n- Connect this feature to their strategic pillars if relevant\n- Update person pages for stakeholders mentioned\n- Link to existing projects if this builds on something\n\n---\n\n## Example Session\n\n**User:** `\u002Fproduct-brief Add notifications to our app`\n\n**Amp:**\n\n```markdown\n## Initial Idea\n\nAdd notifications to our app\n\n---\n\nGreat, let's flesh this out. A few questions to start:\n\n1. What type of notifications are we talking about — push notifications, in-app alerts, email, or all three?\n2. What specific events should trigger notifications?\n3. Who are these notifications for — all users, or specific roles?\n```\n\n**User:** \"Push notifications for now. We want to notify sales reps when a lead takes an action in the product.\"\n\n**Amp:**\n\n```markdown\nGot it — push notifications for sales reps when leads are active. That helps narrow it.\n\nA few more questions:\n\n1. What actions count as notification-worthy? (e.g., login, feature usage, upgrade intent)\n2. Should there be any filtering or preferences? Like \"only notify me about my accounts\"?\n3. What's the business outcome we're driving here — faster response time, more engagement, closing deals faster?\n```\n\n[Conversation continues through phases until PRD is complete]\n\n---\n\n## Integration with Amp System\n\n- **Pillars:** Link PRD to relevant strategic pillar\n- **Quarter Goals:** If this supports a quarterly goal, note it\n- **Week Priorities:** Suggest adding \"finalize PRD\" to this week if urgent\n- **People pages:** Auto-update stakeholders mentioned in the PRD\n- **Tasks:** Offer to create tasks from the PRD's next steps\n\n---\n\n## When to Use This Command\n\n**Use `\u002Fproduct-brief` when:**\n- You have a product idea but struggle to articulate it\n- You need to write a PRD and want help structuring it\n- You're pitching an idea and need to flesh it out\n- You want to validate your thinking with good questions\n\n**Don't use it for:**\n- Simple feature requests (just describe them normally)\n- Already-written PRDs that need editing\n- Technical implementation details (that's engineering's job)\n\n---\n\n## Refinement After Creation\n\nThe PRD isn't set in stone. After creation:\n\n- Say \"refine the success metrics section\" to iterate\n- Say \"add a section on localization\" to expand\n- Say \"this scope is too big, help me cut it down\" to trim\n\nAmp will update the PRD file directly and maintain version history.\n\n---\n\n## Output Quality Checks\n\nBefore finalizing the PRD, verify:\n\n- [ ] Clear problem statement\n- [ ] Specific target audience\n- [ ] Measurable success metrics\n- [ ] Prioritized feature list (MVP vs later)\n- [ ] Explicit out-of-scope items\n- [ ] Key assumptions identified\n- [ ] Dependencies called out\n- [ ] Open questions captured\n\nIf any are missing, prompt user to fill gaps before finalizing.\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark product brief as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `product_brief_created`.\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n","## Purpose\n\nExtract product ideas from your head through guided questioning, then generate a detailed Product Requirements Document (PRD). Designed for product people who have a vision but need help articulating it clearly.\n\n## The Problem This Solves\n\nYou have an idea for a product or feature in your mind, but struggle to explain it comprehensively. This command acts as your product thought partner — asking the right questions to extract what you're envisioning, then structuring it into a PRD ready for a team to execute.\n\n## Usage\n\n```\n\u002Fproduct-brief [initial idea]\n```\n\n**Examples:**\n- `\u002Fproduct-brief Add a notification system to our app`\n- `\u002Fproduct-brief Build a customer feedback portal`\n- `\u002Fproduct-brief Create an onboarding flow for new users`\n- `\u002Fproduct-brief` (prompts you for the idea)\n\n---\n\n## Process Flow\n\n### Phase 1: Capture Initial Idea\n\n**If no idea is provided:**\nAsk: \"What product or feature are you thinking about?\"\n- Wait for their description (1 sentence to several paragraphs)\n- Capture it as the starting point\n\n**If idea is provided:**\nStart with whatever the user provides:\n- Could be 1 sentence or 5 paragraphs\n- Capture it as the starting point\n- Don't judge, just absorb\n\nDisplay:\n\n```markdown\n## Initial Idea\n\n[User's description]\n\n---\n\n**Next:** I'll ask a few questions to understand this better.\n```\n\n---\n\n### Phase 2: Clarifying Questions (Conversational)\n\n**Important:** Ask questions conversationally, not as a survey. 2-3 questions at a time, then wait for answers before asking more.\n\n**Question Strategy:**\n\n**Round 1 (Critical Context):**\n- What problem does this solve?\n- Who is this for?\n- What success looks like?\n\n**Round 2 (Constraints & Scope):**\nBased on Round 1 answers, ask about:\n- Timeline expectations\n- Technical constraints\n- Existing systems to integrate with\n- What's explicitly out of scope\n\n**Round 3 (User Experience):**\n- How do users discover this?\n- What's the core user journey?\n- What actions should be easy vs hard?\n\n**Round 4 (Success & Validation):**\n- How will we know this succeeded?\n- What are we assuming that needs validation?\n- What dependencies exist?\n\n**Adaptive questioning:** If user mentions stakeholders, budget, or other context early, adjust questions accordingly. Don't ask what you already know.\n\nAfter each round, acknowledge answers briefly and transition naturally:\n> \"Got it. That helps me understand [X]. A few more questions about [Y]...\"\n\n---\n\n### Phase 3: Understanding Summary\n\nBefore moving forward, confirm you captured the vision correctly:\n\n```markdown\n## What I Heard\n\n**The Problem:**\n[Synthesized problem statement]\n\n**Target Users:**\n[Who this is for]\n\n**Core Value:**\n[The main benefit\u002Foutcome]\n\n**Key Constraints:**\n[Timeline, technical, scope boundaries]\n\n**Assumptions to Validate:**\n[Things we're assuming but should test]\n\n---\n\n**Does this capture your vision? Type \"yes\" to continue or correct anything above.**\n```\n\nIf user corrects, update and re-confirm.\n\n---\n\n### Phase 4: Spec Doc\n\nUser triggers with: `spec doc` or `create spec`\n\nGenerate structured product spec:\n\n```markdown\n# Product Spec: [Feature\u002FProduct Name]\n\n**Date:** YYYY-MM-DD\n**Owner:** [User's name]\n**Status:** Draft\n\n---\n\n## Executive Summary\n\n[2-3 sentence pitch: what this is and why it matters]\n\n---\n\n## Problem Statement\n\n### Current Situation\n[What exists today]\n\n### Pain Points\n- [Specific pain 1]\n- [Specific pain 2]\n- [Specific pain 3]\n\n### Impact of Inaction\n[What happens if we don't build this]\n\n---\n\n## Target Audience\n\n### Primary Users\n[Who will use this most]\n\n### Secondary Users\n[Who else benefits]\n\n### User Characteristics\n- [Key trait 1]\n- [Key trait 2]\n- [Key trait 3]\n\n---\n\n## Solution Overview\n\n[High-level description of what we're building]\n\n---\n\n## Key Features & Functionality\n\n### Must Have (MVP)\n1. **[Feature 1]**\n   - Description\n   - Why it's critical\n   \n2. **[Feature 2]**\n   - Description\n   - Why it's critical\n\n### Should Have (Phase 2)\n1. **[Feature 3]**\n   - Description\n   - Why it's valuable\n\n### Nice to Have (Future)\n1. **[Feature 4]**\n   - Description\n   - Why it's desirable\n\n---\n\n## Success Metrics\n\n### Primary Metric\n[The one number that matters most]\n\n### Secondary Metrics\n- [Metric 2]\n- [Metric 3]\n\n### Leading Indicators\n[Early signals of success\u002Ffailure]\n\n---\n\n## Assumptions & Risks\n\n### Key Assumptions\n1. [Assumption 1]\n   - How to validate: [Test method]\n   \n2. [Assumption 2]\n   - How to validate: [Test method]\n\n### Risks\n1. **[Risk 1]** — [Mitigation strategy]\n2. **[Risk 2]** — [Mitigation strategy]\n\n---\n\n## Dependencies\n\n### Technical\n- [System\u002FAPI\u002Fservice dependency]\n\n### Team\n- [Who needs to be involved]\n\n### External\n- [Third-party dependencies]\n\n---\n\n## Out of Scope\n\nExplicitly not included:\n- [Thing 1]\n- [Thing 2]\n- [Thing 3]\n\n---\n\n## Open Questions\n\n- [ ] [Question 1]\n- [ ] [Question 2]\n- [ ] [Question 3]\n\n---\n\n**Next Steps:**\n\n- Type `prioritize` to rank features by effort\u002Fimpact\n- Type `design flows` to create detailed user flows\n- Type `create prd` to generate final PRD\n- Type `back` to revise anything above\n```\n\n---\n\n### Phase 5: Prioritization (Optional)\n\nUser triggers with: `prioritize`\n\nCreate effort\u002Fimpact matrix:\n\n```markdown\n## Feature Prioritization\n\n| Feature | Impact | Effort | Priority | Rationale |\n|---------|--------|--------|----------|-----------|\n| [Feature 1] | High | Low | P0 | [Why] |\n| [Feature 2] | High | Medium | P0 | [Why] |\n| [Feature 3] | Medium | Low | P1 | [Why] |\n| [Feature 4] | Low | High | P2 | [Why] |\n\n### Recommended MVP Scope\n\nBased on high impact + reasonable effort:\n1. [Feature 1]\n2. [Feature 2]\n3. [Feature 3]\n\n**Estimated Effort:** [X weeks\u002Fsprints]\n\n---\n\n**Next:**\n- Type `design flows` to create user flows\n- Type `create prd` to generate final PRD\n- Type `back` to revise spec\n```\n\n---\n\n### Phase 6: Design Flows (Optional)\n\nUser triggers with: `design flows`\n\nCreate detailed user flows and screen specs:\n\n```markdown\n## User Flows & Screen Specifications\n\n### Flow 1: [Primary User Journey]\n\n**Entry Point:** [How user arrives]\n\n**Steps:**\n\n#### Step 1: [Screen Name]\n\n**Layout:**\n- [Header elements]\n- [Main content area]\n- [Actions\u002Fbuttons]\n\n**User Actions:**\n- Click [X] → [Outcome]\n- Enter [Y] → [Validation rules]\n- Cancel → [State change]\n\n**Navigation:**\n- Success → [Next screen]\n- Error → [Error state]\n- Back → [Previous screen]\n\n**Validation Rules:**\n- [Field 1]: [Rules]\n- [Field 2]: [Rules]\n\n**States:**\n- Default: [Description]\n- Loading: [What user sees]\n- Error: [Error message]\n- Success: [Confirmation]\n\n---\n\n#### Step 2: [Next Screen]\n\n[Same structure as Step 1]\n\n---\n\n### Flow 2: [Secondary Journey]\n\n[Same structure as Flow 1]\n\n---\n\n**Next:**\n- Type `create prd` to generate final PRD\n- Type `back` to revise flows\n```\n\n---\n\n### Phase 7: Final PRD\n\nUser triggers with: `create prd` or `generate prd`\n\nGenerate comprehensive PRD combining all previous phases:\n\n```markdown\n# Product Requirements Document\n## [Product\u002FFeature Name]\n\n**Author:** [User name]\n**Date:** YYYY-MM-DD\n**Status:** Draft\n**Last Updated:** YYYY-MM-DD\n\n---\n\n## Document Control\n\n| Version | Date | Author | Changes |\n|---------|------|--------|---------|\n| 0.1 | YYYY-MM-DD | [Name] | Initial draft |\n\n---\n\n## Executive Summary\n\n[2-3 paragraphs covering: what, why, who, success]\n\n---\n\n## Background & Context\n\n### Current State\n[What exists today]\n\n### Problem Statement\n[The problem we're solving]\n\n### Opportunity\n[Why now, why us]\n\n---\n\n## Goals & Success Metrics\n\n### Primary Objective\n[The main goal]\n\n### Success Metrics\n\n**Primary:**\n- [Metric 1]: [Target]\n\n**Secondary:**\n- [Metric 2]: [Target]\n- [Metric 3]: [Target]\n\n**Leading Indicators:**\n- [Early signal 1]\n- [Early signal 2]\n\n---\n\n## Target Users\n\n### Primary Audience\n[Detailed description]\n\n### Use Cases\n1. **[Use Case 1]**\n   - As a [user type]\n   - I want to [action]\n   - So that [benefit]\n\n2. **[Use Case 2]**\n   - As a [user type]\n   - I want to [action]\n   - So that [benefit]\n\n---\n\n## Solution Overview\n\n[Comprehensive description of what we're building]\n\n---\n\n## Functional Requirements\n\n### Must Have (P0)\n\n#### Requirement 1: [Name]\n- **Description:** [What it does]\n- **Acceptance Criteria:**\n  - [ ] [Criterion 1]\n  - [ ] [Criterion 2]\n  - [ ] [Criterion 3]\n- **User Story:** As a [X], I want [Y], so that [Z]\n\n#### Requirement 2: [Name]\n[Same structure]\n\n### Should Have (P1)\n\n[Same structure as Must Have]\n\n### Nice to Have (P2)\n\n[Same structure as Must Have]\n\n---\n\n## User Experience\n\n### User Flows\n[Reference to flows from Phase 6, or create if skipped]\n\n### Key Screens\n[High-level screen descriptions]\n\n### Interaction Patterns\n[How users interact with the feature]\n\n---\n\n## Technical Requirements\n\n### Performance\n- [Requirement 1]\n- [Requirement 2]\n\n### Security\n- [Requirement 1]\n- [Requirement 2]\n\n### Integration Points\n- [System 1]: [What needs to connect]\n- [System 2]: [What needs to connect]\n\n### Data Requirements\n- [What data is collected]\n- [Where it's stored]\n- [How it's used]\n\n---\n\n## Design Requirements\n\n### Visual Design\n- [Style guide compliance]\n- [Responsive requirements]\n- [Accessibility standards]\n\n### Content Requirements\n- [Copy needs]\n- [Translation needs]\n- [Asset requirements]\n\n---\n\n## Dependencies & Constraints\n\n### Dependencies\n- **Technical:** [List]\n- **Team:** [Who needs to be involved]\n- **External:** [Third parties]\n\n### Constraints\n- **Timeline:** [Dates\u002Fmilestones]\n- **Budget:** [If applicable]\n- **Technical:** [Platform limitations]\n\n---\n\n## Assumptions & Risks\n\n### Assumptions\n1. [Assumption 1]\n   - **Validation method:** [How to test]\n   - **Impact if wrong:** [Consequence]\n\n2. [Assumption 2]\n   - **Validation method:** [How to test]\n   - **Impact if wrong:** [Consequence]\n\n### Risks\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|------------|--------|------------|\n| [Risk 1] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Strategy] |\n| [Risk 2] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [Strategy] |\n\n---\n\n## Out of Scope\n\nExplicitly not included in this version:\n- [Item 1] — [Why\u002Fwhen it might be included]\n- [Item 2] — [Why\u002Fwhen it might be included]\n- [Item 3] — [Why\u002Fwhen it might be included]\n\n---\n\n## Open Questions\n\n- [ ] [Question 1] — Owner: [Name], Due: [Date]\n- [ ] [Question 2] — Owner: [Name], Due: [Date]\n- [ ] [Question 3] — Owner: [Name], Due: [Date]\n\n---\n\n## Timeline & Milestones\n\n| Milestone | Target Date | Status |\n|-----------|-------------|--------|\n| PRD Complete | [Date] | In Progress |\n| Design Complete | [Date] | Not Started |\n| Dev Complete | [Date] | Not Started |\n| QA Complete | [Date] | Not Started |\n| Launch | [Date] | Not Started |\n\n---\n\n## Stakeholders\n\n| Name | Role | Involvement |\n|------|------|-------------|\n| [Name] | [Role] | [What they do] |\n| [Name] | [Role] | [What they do] |\n\n---\n\n## Appendix\n\n### Research\n[Link to user research, competitive analysis, etc.]\n\n### Design Mockups\n[Links to designs when available]\n\n### Technical Specs\n[Links to technical documentation]\n\n---\n\n**Document Status:** Ready for Review\n\n**Next Actions:**\n- [ ] Review with stakeholders\n- [ ] Refine based on feedback\n- [ ] Get approval to proceed\n- [ ] Hand off to design\u002Fengineering\n\n---\n\n*This PRD was generated using the \u002Fproduct-brief command. Update as needed.*\n```\n\n---\n\n### Phase 8: Save & Integration\n\nAfter generating the PRD:\n\n1. **Save the document:**\n   - Create folder: `04-Projects\u002F[Product Name]\u002F`\n   - Save as: `04-Projects\u002F[Product Name]\u002FPRD.md`\n\n2. **Create person pages** (if stakeholders mentioned):\n   - For each stakeholder mentioned, check if person page exists\n   - Create\u002Fupdate pages in `People\u002FInternal\u002F` or `People\u002FExternal\u002F`\n   - Add note in their page referencing this project\n\n3. **Link to 03-Tasks\u002FTasks.md:**\n   - If user mentioned any immediate actions, suggest creating tasks\n   - Link tasks to the project\n\n4. **Confirm completion:**\n\n```markdown\n## ✅ PRD Created\n\n**Saved to:** `04-Projects\u002F[Product Name]\u002FPRD.md`\n\n**Next Steps:**\n1. Review and refine the PRD\n2. Share with stakeholders for feedback\n3. Use `\u002Fproject-health` to track progress\n4. Create tasks in 03-Tasks\u002FTasks.md when ready to execute\n\n**Want to:**\n- Revise any section → Just tell me what to change\n- Create tasks from this PRD → Say \"create tasks\"\n- Share with stakeholders → I can draft an email\n```\n\n---\n\n## Navigation Commands\n\nAt any phase, users can:\n\n- `back` or `previous` — Return to previous phase\n- `skip to prd` — Jump directly to final PRD\n- `revise [section]` — Edit specific section\n- `start over` — Begin from scratch\n- `save` — Save current progress\n\n---\n\n## Conversational Style\n\n- **Be a thought partner, not an interrogator**\n- Ask follow-up questions when answers reveal gaps\n- Challenge assumptions constructively\n- Suggest alternatives when you spot potential issues\n- Keep momentum — don't let the process feel like homework\n\n**Good:**\n> \"Interesting. If this is for enterprise customers, how do we handle single sign-on? Or is that something we're punting to Phase 2?\"\n\n**Bad:**\n> \"Question 7: Please describe your authentication strategy.\"\n\n---\n\n## Tips for Effectiveness\n\n### For the User\n- Start with whatever you have — even 1 sentence is enough\n- Don't worry about being comprehensive upfront\n- The questions will extract what's in your head\n- You can always revise and refine\n\n### For Amp\n- Listen for what's NOT being said\n- If scope sounds too big, flag it early\n- Connect this feature to their strategic pillars if relevant\n- Update person pages for stakeholders mentioned\n- Link to existing projects if this builds on something\n\n---\n\n## Example Session\n\n**User:** `\u002Fproduct-brief Add notifications to our app`\n\n**Amp:**\n\n```markdown\n## Initial Idea\n\nAdd notifications to our app\n\n---\n\nGreat, let's flesh this out. A few questions to start:\n\n1. What type of notifications are we talking about — push notifications, in-app alerts, email, or all three?\n2. What specific events should trigger notifications?\n3. Who are these notifications for — all users, or specific roles?\n```\n\n**User:** \"Push notifications for now. We want to notify sales reps when a lead takes an action in the product.\"\n\n**Amp:**\n\n```markdown\nGot it — push notifications for sales reps when leads are active. That helps narrow it.\n\nA few more questions:\n\n1. What actions count as notification-worthy? (e.g., login, feature usage, upgrade intent)\n2. Should there be any filtering or preferences? Like \"only notify me about my accounts\"?\n3. What's the business outcome we're driving here — faster response time, more engagement, closing deals faster?\n```\n\n[Conversation continues through phases until PRD is complete]\n\n---\n\n## Integration with Amp System\n\n- **Pillars:** Link PRD to relevant strategic pillar\n- **Quarter Goals:** If this supports a quarterly goal, note it\n- **Week Priorities:** Suggest adding \"finalize PRD\" to this week if urgent\n- **People pages:** Auto-update stakeholders mentioned in the PRD\n- **Tasks:** Offer to create tasks from the PRD's next steps\n\n---\n\n## When to Use This Command\n\n**Use `\u002Fproduct-brief` when:**\n- You have a product idea but struggle to articulate it\n- You need to write a PRD and want help structuring it\n- You're pitching an idea and need to flesh it out\n- You want to validate your thinking with good questions\n\n**Don't use it for:**\n- Simple feature requests (just describe them normally)\n- Already-written PRDs that need editing\n- Technical implementation details (that's engineering's job)\n\n---\n\n## Refinement After Creation\n\nThe PRD isn't set in stone. After creation:\n\n- Say \"refine the success metrics section\" to iterate\n- Say \"add a section on localization\" to expand\n- Say \"this scope is too big, help me cut it down\" to trim\n\nAmp will update the PRD file directly and maintain version history.\n\n---\n\n## Output Quality Checks\n\nBefore finalizing the PRD, verify:\n\n- [ ] Clear problem statement\n- [ ] Specific target audience\n- [ ] Measurable success metrics\n- [ ] Prioritized feature list (MVP vs later)\n- [ ] Explicit out-of-scope items\n- [ ] Key assumptions identified\n- [ ] Dependencies called out\n- [ ] Open questions captured\n\nIf any are missing, prompt user to fill gaps before finalizing.\n\n---\n\n## Track Usage (Silent)\n\nUpdate `System\u002Fusage_log.md` to mark product brief as used.\n\n**Analytics (Silent):**\n\nCall `track_event` with event_name `product_brief_created`.\n\nThis only fires if the user has opted into analytics. No action needed if it returns \"analytics_disabled\".\n",{"name":5,"description":7},"main","5417cad9215b767627c7c947dcb3a0bbe3ebe52d",".claude\u002Fskills\u002Fproduct-brief",0,"https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use","https:\u002F\u002Fgithub.com\u002Fhemory","https:\u002F\u002Fwww.heminthehat.com\u002F","The People Developer | L&D Program Manager | Software Engineer","2026-06-04 23:46:30",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add hemory\u002Famp-legacy-do-not-use --skill product-brief",{"tool":51,"command":52},"bunx","bunx skills add hemory\u002Famp-legacy-do-not-use --skill product-brief",{"tool":54,"command":55},"pnpm","pnpm dlx skills add hemory\u002Famp-legacy-do-not-use --skill product-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproduct-brief\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"resources\u002Fimplementation-playbook.md","REFERENCE","参考文档",14495,"https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fdatabase-migrations-sql-migrations\u002Fresources\u002Fimplementation-playbook.md",[66,101,110,124,139,150],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":80,"publishedAt":31},"01M6D3DVEAHJTTK4W21B15ZZKK","zoom-setup","Connect Zoom to Amp for meeting recordings, scheduling, and transcript context","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fzoom-setup\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"zoom setup","setup","schedule","MCP","review","connect","transcript","search","stats","oauth2","confirmation","context","meetings","process","recordings","surfaces","scheduling","granola","time","distribution",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":31},"01M6D3DRAK8VWESYDZDF8JJDSH","xray","Understand what just happened under the hood - learn AI by seeing it in action","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxray\u002FSKILL.md",[],[103,108,109],"learn","just",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":31},"01M6D3DN7BZQDY6143A2QSDP9A","week-review","Review week's progress with concrete accomplishments (not fake percentages), pattern detection, and goal tracking.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-review\u002FSKILL.md",[116],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[118,85,119,120,121,122,123],"week review","pattern detection","detection","tracking","goal","pattern",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":31},"01M6D3DJ7F1TCFXBBSTQW82WE7","week-plan","Set weekly priorities and plan the week ahead with intelligent suggestions based on goals, calendar shape, and task effort.","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweek-plan\u002FSKILL.md",[],[131,132,133,134,135,136,137,138],"week plan","plan","calendar","SET","shape","goals","task","priorities",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":31},"01M6D3DF90D7RC8ZJE4AW2P9VC","triage","Strategically route orphaned files and extract scattered tasks","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[141,146,147,29,148,149],"tasks","fast","files","route",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":160,"publishedAt":31},"01M6D3DC9BBHK5TASE34SQYXSQ","trello-setup","Connect Trello to Amp for visual Kanban task sync","https:\u002F\u002Fgithub.com\u002Fhemory\u002Famp-legacy-do-not-use\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftrello-setup\u002FSKILL.md",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[161,162,82,163,86,84,164,137,165,166,167,168,169],"trello","trello setup","sync","token","kanban","bun","visual","api","server"]