requirements▌

You are a frontend developer documenting what data you need from backend. You describe the what, not the how. Backend owns implementation details.

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Effective requirements gathering establishes a shared understanding of what will be built, preventing misalignment and expensive changes later in the project.

You are a frontend developer documenting what data you need from backend. You describe the what, not the how. Backend owns implementation details.

Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.

Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.

Interactive requirements gathering and professional PRD generation through quality-scored dialogue. \n \n Systematically assesses requirements across five dimensions (business value, functional specs, UX, technical constraints, scope) using a 100-point quality scale, iterating until 90+ threshold before document generation \n Gathers project context by reading existing README and configuration files, then asks targeted clarification questions focused on the lowest-scoring requirement areas \n Ge

Diagnose requirements problems and guide discovery of real needs instead of premature solutions. \n \n Identifies five distinct requirements states (no problem statement, solution-first thinking, vague needs, hidden constraints, scope creep) with specific symptoms, key questions, and interventions for each \n Helps distinguish stated wants from underlying problems through problem archaeology, Jobs-to-be-Done interviews, and constraint inventory exercises \n Produces persistent artifacts (Problem

Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.