| Sheet 2: REQUIREMENTS | ||||||||
| Category | Use Case | Prompt Template | Variables to Customize | Expected Output | Time Saved | Contributed By | Date Added | Rating |
| Requirements | Extract requirements from RFP | I'm a Business Analyst analyzing an RFP for [PROJECT_TYPE]. Extract all functional and technical requirements and create a table with columns: Requirement ID, Category, Requirement, Priority, Compliance Reference. Categorize as: Security, Integration, UI/UX, Reporting, Data Management, Workflow. Indicate priority as: Mandatory, Highly Desired, Optional. [PASTE_RFP_SECTIONS] | PROJECT_TYPE, RFP_SECTIONS | Requirements table | 2-4 hours | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐⭐ |
| Requirements | Identify missing requirements | I'm a Business Analyst reviewing requirements for [FEATURE_NAME]. Current requirements: [REQUIREMENTS_LIST]. Identify what's missing: edge cases, error handling, security considerations, performance requirements, integration points, data validation, accessibility, audit/logging. | FEATURE_NAME, REQUIREMENTS_LIST | Gap analysis | 30-45 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐⭐ |
| Requirements | Prioritize requirements | I'm a Business Analyst prioritizing requirements for [PROJECT_NAME]. Requirements: [REQUIREMENTS_LIST]. Context: Timeline=[TIMELINE], Budget=[BUDGET], Key Stakeholders=[STAKEHOLDERS]. Categorize using MoSCoW (Must have, Should have, Could have, Won't have). Provide rationale for each. | PROJECT_NAME, REQUIREMENTS_LIST, TIMELINE, BUDGET, STAKEHOLDERS | Prioritized requirements with rationale | 45-60 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |
| Requirements | Create requirements traceability | I'm a Business Analyst creating a traceability matrix for [PROJECT_NAME]. Requirements: [REQUIREMENTS_LIST]. Create a table linking each requirement to: Business Objective, User Story ID, Test Case ID, Design Doc Reference. | PROJECT_NAME, REQUIREMENTS_LIST | Traceability matrix | 60-90 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |
| Requirements | Validate requirements clarity | I'm a Business Analyst reviewing requirements for ambiguity. Requirements: [REQUIREMENTS_LIST]. Identify vague terms (e.g., "fast", "user-friendly", "robust"), missing details, unmeasurable criteria, and conflicting requirements. Suggest specific, measurable alternatives. | REQUIREMENTS_LIST | Clarity assessment with suggestions | 30-45 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |