RFP Analyzer

RFP Analyzer is a senior-level Product Management and System Analyst agent skill designed to deconstruct complex Request for Proposal (RFP) documents, technical specifications, and project requirements. It acts as a bridge between high-level business goals and granular development tasks, enabling product teams to move from chaotic documentation to structured, actionable plans. By applying the 80/20 rule, it filters noise and focuses on the core features that drive 80% of project value, ensuring that engineering teams start development with clear, prioritized scopes.

The skill operates through a rigorous four-phase execution flow: performing a rapid background scan to determine project nature, identifying roles and stakeholder responsibilities, decomposing requirements into a hierarchical structure (System > Module > Feature Group > Feature Item), and extracting non-functional requirements such as performance, security, and compliance. Its most critical output is a categorized list of clarification questions, filtered using a three-tier system (Blocking, Design Details, and Pending Materials) to ensure that the project team only asks essential questions at the right time, preventing scope creep and unnecessary cognitive load.

• Phase 1: Background understanding, project type identification, and budget/launch estimation.

• Phase 2: Role-based stakeholder mapping including End Users, Admins, and Approvers.

• Phase 3: Structural functional decomposition with dependency tracking and complexity estimation (Low/Medium/High).

• Phase 4: Non-functional requirement extraction focusing on performance, compatibility, and security.

• Intelligent question generation based on strict necessity checks, ensuring high-quality engagement with stakeholders.

• Use this skill to transform long-form requirements documents into structured project data for JIRA, Notion, or other project management tools.

• Supports multi-language input; the agent detects the document language and responds accordingly.

• Prioritize blocking questions (P0) to identify architectural risks early in the SDLC.

• Integrates seamlessly with Story Writer and Story Refiner for a full-cycle requirements engineering workflow.

• Operates under the principle of 'reasonable assumptions,' where it identifies implied requirements (e.g., password recovery) and marks them explicitly to minimize uncertainty.