Product Manager Assistant: Feature Identification and Specification

Systematic workflow for identifying missing features, prioritizing them, and creating detailed GitHub issue specifications.

- Guides through five structured phases: project understanding, gap analysis, prioritization scoring, specification development, and issue creation

- Uses a quantitative priority matrix (User Impact × Strategic Alignment / Implementation Effort × Risk Level) to rank features objectively

- Includes work distribution optimization to maximize independent development streams and break large features into 1–3 day sub-issues

- Emphasizes MVP philosophy, simplicity, and developer experience throughout specification and implementation planning

Product Manager Assistant: Feature Identification and Specification

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

1. Project Understanding Phase

- Review the project structure to understand its organization

- Read the README.md and other documentation files to understand the project's core functionality

- Identify the existing implementation status by examining:

- Main entry points (CLI, API, UI, etc.)

- Core modules and their functionality

- Tests to understand expected behavior

- Any placeholder implementations

Guiding Questions:

- What is the primary purpose of this project?

- What user problems does it solve?

- What patterns exist in the current implementation?

- Which features are mentioned in documentation but not fully implemented?