Cursor rule

1---
2alwaysApply: false
3---
4 
5# NFR Requirements
6 
7## Prerequisites
8- Functional Design must be complete for the unit
9- Unit functional design artifacts must be available
10- Execution plan must indicate NFR Requirements stage should execute
11 
12## Overview
13Determine non-functional requirements for the unit and make tech stack choices.
14 
15## Steps to Execute
16 
17### Step 1: Analyze Functional Design
18- Read functional design artifacts from `aidlc-docs/construction/{unit-name}/functional-design/`
19- Understand business logic complexity and requirements
20 
21### Step 2: Create NFR Requirements Plan
22- Generate plan with checkboxes [] for NFR assessment
23- Focus on scalability, performance, availability, security
24- Each step should have a checkbox []
25 
26### Step 3: Generate Context-Appropriate Questions
27**DIRECTIVE**: Thoroughly analyze the functional design to identify ALL areas where NFR clarification would improve system quality and architecture decisions. Be proactive in asking questions to ensure comprehensive NFR coverage.
28 
29**CRITICAL**: Default to asking questions when there is ANY ambiguity or missing detail that could affect system quality. It's better to ask too many questions than to make incorrect NFR assumptions.
30 
31- EMBED questions using [Answer]: tag format
32- Focus on ANY ambiguities, missing information, or areas needing clarification
33- Generate questions wherever user input would improve NFR and tech stack decisions
34- **When in doubt, ask the question** - overconfidence leads to poor system quality
35 
36**Question categories to evaluate** (consider ALL categories):
37- **Scalability Requirements** - Ask about expected load, growth patterns, scaling triggers, and capacity planning
38- **Performance Requirements** - Ask about response times, throughput, latency, and performance benchmarks
39- **Availability Requirements** - Ask about uptime expectations, disaster recovery, failover, and business continuity
40- **Security Requirements** - Ask about data protection, compliance, authentication, authorization, and threat models
41- **Tech Stack Selection** - Ask about technology preferences, constraints, existing systems, and integration requirements
42- **Reliability Requirements** - Ask about error handling, fault tolerance, monitoring, and alerting needs
43- **Maintainability Requirements** - Ask about code quality, documentation, testing, and operational requirements
44- **Usability Requirements** - Ask about user experience, accessibility, and interface requirements
45 
46### Step 4: Store Plan
47- Save as `aidlc-docs/construction/plans/{unit-name}-nfr-requirements-plan.md`
48- Include all [Answer]: tags for user input
49 
50### Step 5: Collect and Analyze Answers
51- Wait for user to complete all [Answer]: tags
52- **MANDATORY**: Carefully review ALL responses for vague or ambiguous answers
53- **CRITICAL**: Add follow-up questions for ANY unclear responses - do not proceed with ambiguity
54- Look for responses like "depends", "maybe", "not sure", "mix of", "somewhere between", "standard", "typical"
55- Create clarification questions file if ANY ambiguities are detected
56- **Do not proceed until ALL ambiguities are resolved**
57 
58### Step 6: Generate NFR Requirements Artifacts
59- Create `aidlc-docs/construction/{unit-name}/nfr-requirements/nfr-requirements.md`
60- Create `aidlc-docs/construction/{unit-name}/nfr-requirements/tech-stack-decisions.md`
61 
62### Step 7: Present Completion Message
63- Present completion message in this structure:
64     1. **Completion Announcement** (mandatory): Always start with this:
65 
66```markdown
67# 📊 NFR Requirements Complete - [unit-name]
68```
69 
70     2. **AI Summary** (optional): Provide structured bullet-point summary of NFR requirements
71        - Format: "NFR requirements assessment has identified [description]:"
72        - List key scalability, performance, availability requirements (bullet points)
73        - List security and compliance requirements identified
74        - Mention tech stack decisions and rationale
75        - DO NOT include workflow instructions ("please review", "let me know", "proceed to next phase", "before we proceed")
76        - Keep factual and content-focused
77     3. **Formatted Workflow Message** (mandatory): Always end with this exact format:
78 
79```markdown
80> **📋 <u>**REVIEW REQUIRED:**</u>**  
81> Please examine the NFR requirements at: `aidlc-docs/construction/[unit-name]/nfr-requirements/`
82 
83 
84 
85> **🚀 <u>**WHAT'S NEXT?**</u>**
86>
87> **You may:**
88>
89> 🔧 **Request Changes** - Ask for modifications to the NFR requirements based on your review  
90> ✅ **Continue to Next Stage** - Approve NFR requirements and proceed to **[next-stage-name]**
91 
92---
93```
94 
95### Step 8: Wait for Explicit Approval
96- Do not proceed until the user explicitly approves the NFR requirements
97- Approval must be clear and unambiguous
98- If user requests changes, update the requirements and repeat the approval process
99 
100### Step 9: Record Approval and Update Progress
101- Log approval in audit.md with timestamp
102- Record the user's approval response with timestamp
103- Mark NFR Requirements stage complete in aidlc-state.md
104