product-manager

Malicious tool definition detected

Tool: REFERENCE.md [1/3] Description: # Product Manager Reference Guide This document provides detailed guidance on prioritization frameworks, requirements patterns, and best practices for product management activities.

Tool: REFERENCE.md [2/3] Description: Impact:** Negative when present - **Examples:** - Unwanted notifications - Forced upsells - Overly complex interfaces - **Strategy:** Identify and remove **Feature Evolution:** ``` Excitement → Performance → Basic → Indifferent/Reverse (Innovation) → (Standard) → (Expected) → (Obsolete) ``` **Application Example:** ``` Product: Project Management Tool Basic Features: - Create/edit/delete tasks - Assign tasks to users - Set due dates - Mark tasks complete → M

Tool: REFERENCE.md [3/3] Description: on the login page When they enter valid credentials and click "Login" Then they are redirected to the dashboard within 2 seconds And their session token is stored securely ``` ## Framework Selection Guide **Choose MoSCoW when:** - You have a fixed timeline - Need stakeholder alignment - Defining MVP scope - Simple, fast prioritization needed **Choose RICE when:** - You have quantitative data - Comparing many features - Need objective prioritization - Resourc

Malicious tool definition detected

Tool: SKILL.md [1/2] Description: --- name: product-manager description: Product requirements and planning specialist.

Tool: SKILL.md [2/2] Description: projects ### Available Scripts - `scripts/prioritize.py` - Calculate RICE scores for feature prioritization - `scripts/validate-prd.sh` - Validate PRD has all required sections ### Resources - `resources/prioritization-frameworks.md` - Detailed framework reference ## Validation Checklist Before completing a PRD or tech spec, verify: - [ ] All requirements have unique IDs - [ ] Every requirement has priority assigned - [ ] All requirements have acceptance criteri

Malicious tool definition detected

Tool: resources/prioritization-frameworks.md [1/4] Description: # Prioritization Frameworks - Detailed Reference This document provides comprehensive guidance on feature and requirement prioritization frameworks used in product management.

Tool: resources/prioritization-frameworks.md [2/4] Description: Cosmetic changes --- #### Confidence **Definition:** How certain are you about your Reach and Impact estimates?

Tool: resources/prioritization-frameworks.md [3/4] Description: voicemail - **Amazon:** One-click ordering, personalized recommendations - **Netflix:** Download for offline viewing, smart downloads - **Uber:** Live driver tracking, fare estimates **Strategy:** - Source of competitive advantage - Requires innovation and creativity - High risk, high reward - Become Performance features over time - Opportunity for PR and buzz **Warning:** What excites early adopters may not excite mainstream users.

Tool: resources/prioritization-frameworks.md [4/4] Description: Many features, data-driven orgs | Medium | Medium | Analytics data | | Kano | Understanding satisfaction drivers | High | High | User research | | Value vs.

Malicious tool definition detected

Tool: scripts/prioritize.py Description: #!/usr/bin/env python3 """ RICE Score Calculator for Feature Prioritization RICE = (Reach × Impact × Confidence) / Effort Usage: python prioritize.py # Interactive mode python prioritize.py --batch features.csv # Batch mode from CSV python prioritize.py --help # Show help Interactive mode will prompt for: - Reach: Number of users affected per time period - Impact: Value per user (0.25, 0.5, 1, 2, 3) - Confidence: Certainty

Malicious tool definition detected

Tool: scripts/validate-prd.sh Description: #!/bin/bash # # PRD Validation Script # # Validates that a Product Requirements Document contains all required sections # and meets quality standards.

Malicious tool definition detected

Tool: templates/prd.template.md [1/2] Description: # Product Requirements Document (PRD) **Project Name:** {{PROJECT_NAME}} **Document Version:** {{VERSION}} **Date:** {{DATE}} **Author:** {{AUTHOR}} **Status:** {{STATUS}} --- ## Document Control | Version | Date | Author | Changes | |---------|------|--------|---------| | {{VERSION}} | {{DATE}} | {{AUTHOR}} | Initial draft | ## Approvals | Role | Name | Signature | Date | |------|------|-----------|------| | Product Owner | | | | | Engineering

Tool: templates/prd.template.md [2/2] Description: | Requirement ID | Business Goal | Epic | User Story | Test Case | Status | |----------------|---------------|------|------------|-----------|--------| | FR-001 | {{GOAL_1}} | EPIC-001 | STORY-001 | TC-001 | {{STATUS}} | | FR-002 | {{GOAL_1}} | EPIC-001 | STORY-002 | TC-002 | {{STATUS}} | | FR-003 | {{GOAL_2}} | EPIC-002 | STORY-003 | TC-003 | {{STATUS}} | | NFR-001 | {{GOAL_3}} | N/A | N/A | TC-015 | {{STATUS}} | --- ## Appendix ### A.

Malicious tool definition detected

Tool: templates/tech-spec.template.md Description: # Technical Specification **Project Name:** {{PROJECT_NAME}} **Version:** {{VERSION}} **Date:** {{DATE}} **Author:** {{AUTHOR}} **Status:** {{STATUS}} --- ## Overview ### Problem Statement {{PROBLEM_STATEMENT}} ### Proposed Solution {{SOLUTION_OVERVIEW}} ### Goals - {{GOAL_1}} - {{GOAL_2}} - {{GOAL_3}} --- ## Scope ### In Scope - {{IN_SCOPE_1}} - {{IN_SCOPE_2}} - {{IN_SCOPE_3}} ### Out of Scope - {{OUT_OF_SCOPE_1}} - {{OUT_OF_SCOPE_2}} - {{OUT_O