From aaa9c1a163d8c57a3bfeade996479292954ec383 Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Tue, 25 Nov 2025 23:02:32 +0100 Subject: [PATCH 1/6] Update 2.2_gen_epics.md draft output fomrat --- .cursor/commands/2.planning/2.2_gen_epics.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index 75ce27f..d7b349a 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -21,4 +21,17 @@ ## Task - Generate Jira Epics from the Components - 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 Jira Epic numbers corresponding to each component. \ No newline at end of file + - Generate draw.io components diagram based on previous diagram shows relations between components and current Jira Epic number, corresponding to each component. + +## Output + Creatre jira epics + Each epic shoulf have the following structire + Each epic must correcspond to the System design block + - Integration tests + - Summary + - Detailed description + - Input data for this specific test scenario + - Expected result + - Maximum expected time to get result + + From acf7650e82e6d638de7f7b023ad5fb1553b26470 Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Tue, 25 Nov 2025 23:02:58 +0100 Subject: [PATCH 2/6] Update 2.2_gen_epics.md --- .cursor/commands/2.planning/2.2_gen_epics.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index d7b349a..e546b00 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -24,9 +24,7 @@ - Generate draw.io components diagram based on previous diagram shows relations between components and current Jira Epic number, corresponding to each component. ## Output - Creatre jira epics - Each epic shoulf have the following structire - Each epic must correcspond to the System design block + Epic format: - Integration tests - Summary - Detailed description From ca518d4dfeef9afc644912c3e091b560692f8113 Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Tue, 25 Nov 2025 23:03:10 +0100 Subject: [PATCH 3/6] Update 2.2_gen_epics.md --- .cursor/commands/2.planning/2.2_gen_epics.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index e546b00..fa35a22 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -31,5 +31,6 @@ - Input data for this specific test scenario - Expected result - Maximum expected time to get result - + + Example: From 4af14d0328157620578842784de4caaecacc9958 Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Tue, 25 Nov 2025 23:04:08 +0100 Subject: [PATCH 4/6] Update 2.2_gen_epics.md --- .cursor/commands/2.planning/2.2_gen_epics.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index fa35a22..5c3be78 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -32,5 +32,8 @@ - Expected result - Maximum expected time to get result - Example: +## Example + + +## Notes From f8390329cd39fe95820cce6b9d457972062b2857 Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Tue, 25 Nov 2025 23:05:32 +0100 Subject: [PATCH 5/6] Update 2.2_gen_epics.md --- .cursor/commands/2.planning/2.2_gen_epics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index 5c3be78..cc64084 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -16,7 +16,7 @@ `@docs/01_solution/solution_draft.md` ## Role - You are a professional product manager + You are a world class product manager ## Task - Generate Jira Epics from the Components From a329ad084c27101a9b8f814152bcf90a1bce3eed Mon Sep 17 00:00:00 2001 From: Dennis Popov Date: Thu, 27 Nov 2025 00:48:35 +0100 Subject: [PATCH 6/6] Update 2.2_gen_epics.md epic format described --- .cursor/commands/2.planning/2.2_gen_epics.md | 51 +++++++++++++++----- 1 file changed, 40 insertions(+), 11 deletions(-) diff --git a/.cursor/commands/2.planning/2.2_gen_epics.md b/.cursor/commands/2.planning/2.2_gen_epics.md index cc64084..7a97347 100644 --- a/.cursor/commands/2.planning/2.2_gen_epics.md +++ b/.cursor/commands/2.planning/2.2_gen_epics.md @@ -25,15 +25,44 @@ ## Output Epic format: - - Integration tests - - Summary - - Detailed description - - Input data for this specific test scenario - - Expected result - - Maximum expected time to get result + - Epic Name [Component] – [Outcome] + - Example: Data Ingestion – Near-real-time pipeline + - Epic Summary (1–2 sentences) + - What we are building + why it matters + - Problem / Context + - Current state, pain points, constraints, business opportunities, Links to architecture decision records or diagrams + - Scope. Detailed description + - In Scope. Bullet list of capabilities (not tasks) + - Out-of-scope. Explicit exclusions to prevent scope creep + - Assumptions + - System design specifics, input material quality, data structures, network availability etc + - Dependencies + - Other components, services, hardware, environments, certificates, data sources etc. + - 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 + - Design & Architecture (links) + - High-level diagram link , Data flow, sequence diagrams, schemas etc + - Definition of Done (Epic-level) + - Feature list per epic scope + - Automated tests (unit/integration/e2e) + minimum coverage threshold met + - Runbooks if applicable + - Documentation updated + - Acceptance Criteria (measurable) + - Risks & Mitigations + - Top 5 risks (technical + delivery) with mitigation owners or systems involved + - Label epic + - component: + - env:prod|stg + - type:platform|data|integration -## Example - - -## Notes - + - Jira Issue Breakdown + - Create consistent child issues under the epic + - Spikes + - Tasks + - Technical enablers + +