review of all AI-dev system #01

add refactoring phase
complete implementation phase
fix wrong links and file names

.cursor/commands/2.planning/2.20_plan_jira_epics.md

@@ -1,4 +1,4 @@
-# generate Jira Epics
+# Generate Jira Epics
 
 ## Initial data:
  - Problem description: `@_docs/00_problem/problem_description.md`
@@ -6,12 +6,15 @@
  - Restrictions: `@_docs/00_problem/restrictions.md`
  - Acceptance criteria: `@_docs/00_problem/acceptance_criteria.md`
  - Full Solution Description: `@_docs/01_solution/solution.md`
+ - Components: `@_docs/02_components`
 
 ## Role
   You are a world class product manager
 
 ## Task
-  - Generate Jira Epics from the Components Using Jira MCP
+  - Generate Jira Epics from the Components using Jira MCP
+  - Order epics by dependency (which must be done first)
+  - Include rough effort estimation per epic
   - Ensure each epic has clear goal and acceptance criteria, verify it with acceptance criteria
   - Generate draw.io components diagram based on previous diagram shows relations between components and current Jira Epic number, corresponding to each component.
 
@@ -29,17 +32,20 @@
  - Assumptions
   - System design specifics, input material quality, data structures, network availability etc
  - Dependencies
+  - Other epics that must be completed first
   - Other components, services, hardware, environments, certificates, data sources etc.
+ - Effort Estimation
+  - T-shirt size (S/M/L/XL) or story points range
  - Users / Consumers
   - Internal, External, Systems, Short list of the key use cases.
  - Requirements
   - Functional - API expectations, events, data handling, idempotency, retry behavior etc
-  - Non-functional -Availability, latency, throughput, scalability, processing limits, data retention etc
-  - Security/Compliance - Authentication, encryption, secrets, logging, SOC2/ISO is applicable
+  - Non-functional - Availability, latency, throughput, scalability, processing limits, data retention etc
+  - Security/Compliance - Authentication, encryption, secrets, logging, SOC2/ISO if applicable
  - Design & Architecture (links)
-  - High-level diagram link , Data flow, sequence diagrams, schemas etc
+  - High-level diagram link, Data flow, sequence diagrams, schemas etc
  - Definition of Done (Epic-level)
-  - Feature list  per epic scope
+  - Feature list per epic scope
   - Automated tests (unit/integration/e2e) + minimum coverage threshold met
   - Runbooks if applicable
   - Documentation updated
@@ -57,6 +63,5 @@
    - Tasks
    - Technical enablers
   
-  ## Notes
-   - Be as much concise as possible in formulating epics. The less words with the same meaning - the better epic is.
-  
+## Notes
+ - Be as much concise as possible in formulating epics. The less words with the same meaning - the better epic is.