Cursor rule

1---
2alwaysApply: false
3---
4 
5# Units Generation - Detailed Steps
6 
7## Overview
8This stage decomposes the system into manageable units of work through two integrated parts:
9- **Part 1 - Planning**: Create decomposition plan with questions, collect answers, analyze for ambiguities, get approval
10- **Part 2 - Generation**: Execute approved plan to generate unit artifacts
11 
12**DEFINITION**: A unit of work is a logical grouping of stories for development purposes. For microservices, each unit becomes an independently deployable service. For monoliths, the single unit represents the entire application with logical modules.
13 
14**Terminology**: Use "Service" for independently deployable components, "Module" for logical groupings within a service, "Unit of Work" for planning context.
15 
16## Prerequisites
17- Workspace Detection must be complete
18- Requirements Analysis recommended (provides functional scope)
19- User Stories recommended (stories map to units)
20- Application Design stage REQUIRED (determines components, methods, and services)
21- Execution plan must indicate Design stage should execute
22 
23---
24 
25# PART 1: PLANNING
26 
27## Step 1: Create Unit of Work Plan
28- Generate plan with checkboxes [] for decomposing system into units of work
29- Focus on breaking down the system into manageable development units
30- Each step and sub-step should have a checkbox []
31 
32## Step 2: Include Mandatory Unit Artifacts in Plan
33**ALWAYS** include these mandatory artifacts in the unit plan:
34- [ ] Generate `aidlc-docs/inception/application-design/unit-of-work.md` with unit definitions and responsibilities
35- [ ] Generate `aidlc-docs/inception/application-design/unit-of-work-dependency.md` with dependency matrix
36- [ ] Generate `aidlc-docs/inception/application-design/unit-of-work-story-map.md` mapping stories to units
37- [ ] **Greenfield only**: Document code organization strategy in `unit-of-work.md` (see code-generation.md for structure patterns)
38- [ ] Validate unit boundaries and dependencies
39- [ ] Ensure all stories are assigned to units
40 
41## Step 3: Generate Context-Appropriate Questions
42**DIRECTIVE**: Thoroughly analyze the requirements, stories, and application design to identify ALL areas where clarification would improve unit decomposition quality. Be proactive in asking questions to ensure comprehensive coverage of decomposition concerns.
43 
44**CRITICAL**: Default to asking questions when there is ANY ambiguity or missing detail that could affect unit boundaries or decomposition quality. It's better to ask too many questions than to make incorrect assumptions about how the system should be decomposed.
45 
46**MANDATORY**: Evaluate ALL of the following categories by asking targeted questions about each. For each category, determine applicability based on evidence from the requirements, stories, and application design -- do not skip categories without explicit justification:
47 
48- EMBED questions using [Answer]: tag format
49- Focus on ANY ambiguities, missing information, or areas needing clarification
50- Generate questions wherever user input would improve decomposition decisions
51- **When in doubt, ask the question** - overconfidence leads to poor unit boundaries
52 
53**Question categories to evaluate** (consider ALL categories):
54- **Story Grouping** - Ask about grouping strategy, story affinity, and logical clustering approaches
55- **Dependencies** - Ask about integration approach, shared resources, and inter-unit communication patterns
56- **Team Alignment** - Ask about team structure, ownership boundaries, and collaboration models
57- **Technical Considerations** - Ask about scalability/deployment requirements that may differ across units
58- **Business Domain** - Ask about domain boundaries, bounded contexts, and business capability alignment
59- **Code Organization (Greenfield multi-unit only)** - Ask about deployment model and directory structure preferences
60 
61## Step 4: Store UOW Plan
62- Save as `aidlc-docs/inception/plans/unit-of-work-plan.md`
63- Include all [Answer]: tags for user input
64- Ensure plan covers all aspects of system decomposition
65 
66## Step 5: Request User Input
67- Ask user to fill [Answer]: tags directly in the plan document
68- Emphasize importance of decomposition decisions
69- Provide clear instructions on completing the [Answer]: tags
70 
71## Step 6: Collect Answers
72- Wait for user to provide answers to all questions using [Answer]: tags in the document
73- Do not proceed until ALL [Answer]: tags are completed
74- Review the document to ensure no [Answer]: tags are left blank
75 
76## Step 7: ANALYZE ANSWERS (MANDATORY)
77Before proceeding, you MUST carefully review all user answers for:
78- **Vague or ambiguous responses**: "mix of", "somewhere between", "not sure", "depends"
79- **Undefined criteria or terms**: References to concepts without clear definitions
80- **Contradictory answers**: Responses that conflict with each other
81- **Missing generation details**: Answers that lack specific guidance
82- **Answers that combine options**: Responses that merge different approaches without clear decision rules
83 
84## Step 8: MANDATORY Follow-up Questions
85If the analysis in step 7 reveals ANY ambiguous answers, you MUST:
86- Add specific follow-up questions to the plan document using [Answer]: tags
87- DO NOT proceed to approval until all ambiguities are resolved
88- Examples of required follow-ups:
89  - "You mentioned 'mix of A and B' - what specific criteria should determine when to use A vs B?"
90  - "You said 'somewhere between A and B' - can you define the exact middle ground approach?"
91  - "You indicated 'not sure' - what additional information would help you decide?"
92  - "You mentioned 'depends on complexity' - how do you define complexity levels?"
93 
94## Step 9: Request Approval
95- Ask: "**Unit of work plan complete. Review the plan in aidlc-docs/inception/plans/unit-of-work-plan.md. Ready to proceed to generation?**"
96- DO NOT PROCEED until user confirms
97 
98## Step 10: Log Approval
99- Log prompt and response in audit.md with timestamp
100- Use ISO 8601 timestamp format
101- Include complete approval prompt text
102 
103## Step 11: Update Progress
104- Mark Units Planning complete in aidlc-state.md
105- Update the "Current Status" section
106- Prepare for transition to Units Generation
107 
108---
109 
110# PART 2: GENERATION
111 
112## Step 12: Load Unit of Work Plan
113- [ ] Read the complete plan from `aidlc-docs/inception/plans/unit-of-work-plan.md`
114- [ ] Identify the next uncompleted step (first [ ] checkbox)
115- [ ] Load the context and requirements for that step
116 
117## Step 13: Execute Current Step
118- [ ] Perform exactly what the current step describes
119- [ ] Generate unit artifacts as specified in the plan
120- [ ] Follow the approved decomposition approach from Planning
121- [ ] Use the criteria and boundaries specified in the plan
122 
123## Step 14: Update Progress
124- [ ] Mark the completed step as [x] in the unit of work plan
125- [ ] Update `aidlc-docs/aidlc-state.md` current status
126- [ ] Save all generated artifacts
127 
128## Step 15: Continue or Complete
129- [ ] If more steps remain, return to Step 12
130- [ ] If all steps complete, verify units are ready for design stages
131- [ ] Mark Units Generation stage as complete
132 
133## Step 16: Present Completion Message
134 
135```markdown
136# 🔧 Units Generation Complete
137 
138[AI-generated summary of units and decomposition created in bullet points]
139 
140> **📋 <u>**REVIEW REQUIRED:**</u>**  
141> Please examine the units generation artifacts at: `aidlc-docs/inception/application-design/`
142 
143> **🚀 <u>**WHAT'S NEXT?**</u>**
144>
145> **You may:**
146>
147> 🔧 **Request Changes** - Ask for modifications to the units generation if required
148> ✅ **Approve & Continue** - Approve units and proceed to **CONSTRUCTION PHASE**
149```
150 
151## Step 17: Wait for Explicit Approval
152- Do not proceed until the user explicitly approves the units generation
153- Approval must be clear and unambiguous
154- If user requests changes, update the units and repeat the approval process
155 
156## Step 18: Record Approval Response
157- Log the user's approval response with timestamp in `aidlc-docs/audit.md`
158- Include the exact user response text
159- Mark the approval status clearly
160 
161## Step 19: Update Progress
162- Mark Units Generation stage complete in `aidlc-docs/aidlc-state.md`
163- Update the "Current Status" section
164- Prepare for transition to CONSTRUCTION PHASE
165 
166---
167 
168## Critical Rules
169 
170### Planning Phase Rules
171- Generate ONLY context-relevant questions
172- Use [Answer]: tag format for all questions
173- Analyze all answers for ambiguities before proceeding
174- Resolve ALL ambiguities with follow-up questions
175- Get explicit user approval before generation
176 
177### Generation Phase Rules
178- **NO HARDCODED LOGIC**: Only execute what's written in the unit of work plan
179- **FOLLOW PLAN EXACTLY**: Do not deviate from the step sequence
180- **UPDATE CHECKBOXES**: Mark [x] immediately after completing each step
181- **USE APPROVED APPROACH**: Follow the decomposition methodology from Planning
182- **VERIFY COMPLETION**: Ensure all unit artifacts are complete before proceeding
183 
184## Completion Criteria
185- All planning questions answered and ambiguities resolved
186- User approval obtained for the plan
187- All steps in unit of work plan marked [x]
188- All unit artifacts generated according to plan:
189  - `unit-of-work.md` with unit definitions
190  - `unit-of-work-dependency.md` with dependency matrix
191  - `unit-of-work-story-map.md` with story mappings
192- Units verified and ready for per-unit design stages
193