Cursor rule

1---
2alwaysApply: false
3---
4 
5# Functional Design
6 
7## Purpose
8**Detailed business logic design per unit**
9 
10Functional Design focuses on:
11- Detailed business logic and algorithms for the unit
12- Domain models with entities and relationships
13- Detailed business rules, validation logic, and constraints
14- Technology-agnostic design (no infrastructure concerns)
15 
16**Note**: This builds upon high-level component design from Application Design (INCEPTION phase)
17 
18## Prerequisites
19- Units Generation must be complete
20- Unit of work artifacts must be available
21- Application Design recommended (provides high-level component structure)
22- Execution plan must indicate Functional Design stage should execute
23 
24## Overview
25Design detailed business logic for the unit, technology-agnostic and focused purely on business functions.
26 
27## Steps to Execute
28 
29### Step 1: Analyze Unit Context
30- Read unit definition from `aidlc-docs/inception/application-design/unit-of-work.md`
31- Read assigned stories from `aidlc-docs/inception/application-design/unit-of-work-story-map.md`
32- Understand unit responsibilities and boundaries
33 
34### Step 2: Create Functional Design Plan
35- Generate plan with checkboxes [] for functional design
36- Focus on business logic, domain models, business rules
37- Each step should have a checkbox []
38 
39### Step 3: Generate Context-Appropriate Questions
40**DIRECTIVE**: Thoroughly analyze the unit definition and functional design artifacts to identify ALL areas where clarification would improve the functional design. Be proactive in asking questions to ensure comprehensive understanding.
41 
42**CRITICAL**: Default to asking questions when there is ANY ambiguity or missing detail that could affect functional design quality. It's better to ask too many questions than to make incorrect assumptions.
43 
44- EMBED questions using [Answer]: tag format
45- Focus on ANY ambiguities, missing information, or areas needing clarification
46- Generate questions wherever user input would improve functional design decisions
47- **When in doubt, ask the question** - overconfidence leads to poor designs
48 
49**Question categories to consider** (evaluate ALL categories):
50- **Business Logic Modeling** - Ask about core entities, workflows, data transformations, and business processes
51- **Domain Model** - Ask about domain concepts, entity relationships, data structures, and business objects
52- **Business Rules** - Ask about decision rules, validation logic, constraints, and business policies
53- **Data Flow** - Ask about data inputs, outputs, transformations, and persistence requirements
54- **Integration Points** - Ask about external system interactions, APIs, and data exchange
55- **Error Handling** - Ask about error scenarios, validation failures, and exception handling
56- **Business Scenarios** - Ask about edge cases, alternative flows, and complex business situations
57- **Frontend Components** (if applicable) - Ask about UI component structure, user interactions, state management, and form handling
58 
59### Step 4: Store Plan
60- Save as `aidlc-docs/construction/plans/{unit-name}-functional-design-plan.md`
61- Include all [Answer]: tags for user input
62 
63### Step 5: Collect and Analyze Answers
64- Wait for user to complete all [Answer]: tags
65- **MANDATORY**: Carefully review ALL responses for vague or ambiguous answers
66- **CRITICAL**: Add follow-up questions for ANY unclear responses - do not proceed with ambiguity
67- Look for responses like "depends", "maybe", "not sure", "mix of", "somewhere between"
68- Create clarification questions file if ANY ambiguities are detected
69- **Do not proceed until ALL ambiguities are resolved**
70 
71### Step 6: Generate Functional Design Artifacts
72- Create `aidlc-docs/construction/{unit-name}/functional-design/business-logic-model.md`
73- Create `aidlc-docs/construction/{unit-name}/functional-design/business-rules.md`
74- Create `aidlc-docs/construction/{unit-name}/functional-design/domain-entities.md`
75- If unit includes frontend/UI: Create `aidlc-docs/construction/{unit-name}/functional-design/frontend-components.md`
76  - Component hierarchy and structure
77  - Props and state definitions for each component
78  - User interaction flows
79  - Form validation rules
80  - API integration points (which backend endpoints each component uses)
81 
82### Step 7: Present Completion Message
83- Present completion message in this structure:
84     1. **Completion Announcement** (mandatory): Always start with this:
85 
86```markdown
87# 🔧 Functional Design Complete - [unit-name]
88```
89 
90     2. **AI Summary** (optional): Provide structured bullet-point summary of functional design
91        - Format: "Functional design has created [description]:"
92        - List key business logic models and entities (bullet points)
93        - List business rules and validation logic defined
94        - Mention domain model structure and relationships
95        - DO NOT include workflow instructions ("please review", "let me know", "proceed to next phase", "before we proceed")
96        - Keep factual and content-focused
97     3. **Formatted Workflow Message** (mandatory): Always end with this exact format:
98 
99```markdown
100> **📋 <u>**REVIEW REQUIRED:**</u>**  
101> Please examine the functional design artifacts at: `aidlc-docs/construction/[unit-name]/functional-design/`
102 
103 
104 
105> **🚀 <u>**WHAT'S NEXT?**</u>**
106>
107> **You may:**
108>
109> 🔧 **Request Changes** - Ask for modifications to the functional design based on your review  
110> ✅ **Continue to Next Stage** - Approve functional design and proceed to **[next-stage-name]**
111 
112---
113```
114 
115### Step 8: Wait for Explicit Approval
116- Do not proceed until the user explicitly approves the functional design
117- Approval must be clear and unambiguous
118- If user requests changes, update the design and repeat the approval process
119 
120### Step 9: Record Approval and Update Progress
121- Log approval in audit.md with timestamp
122- Record the user's approval response with timestamp
123- Mark Functional Design stage complete in aidlc-state.md
124