From 175c6e050098582bf89be1f377776cbb68ff3cef Mon Sep 17 00:00:00 2001 From: VinPropane Date: Tue, 7 Apr 2026 00:20:01 -0400 Subject: [PATCH] =?UTF-8?q?chore:=20document=20Jira=20epic=E2=86=92story?= =?UTF-8?q?=20+=20labels=20(no=20Feature=20issues)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Module/slice grouping below epics is labels on stories only; Feature work items are not used. Cross-link from jira-git-naming, story kickoff, and documentation alignment table. --- .cursor/rules/jira-git-naming.md | 4 ++++ .cursor/rules/story-kickoff.md | 1 + docs/decomposition/README.md | 8 +++++++- .../modules/documentation_and_implementation_alignment.md | 1 + 4 files changed, 13 insertions(+), 1 deletion(-) diff --git a/.cursor/rules/jira-git-naming.md b/.cursor/rules/jira-git-naming.md index c9ab069..2dbf264 100644 --- a/.cursor/rules/jira-git-naming.md +++ b/.cursor/rules/jira-git-naming.md @@ -7,6 +7,10 @@ alwaysApply: true Project key in Jira is **`NEON`** unless a different key is used for the issue (match the issue you are implementing). +## Issue hierarchy + +Tracked work is **Epic → Story** (or Task/Bug). **Do not** create Jira **Feature** issues: module- or slice-level grouping below an epic is **labels on the story** only (prefer decomposition module ids such as **E1.M1** when they fit). Canonical wording: [decomposition README — Jira alignment](../../docs/decomposition/README.md#jira-alignment). + ## Branch names - Put the **Jira key first**, then a short **kebab-case** slug (and optional type). The key must be the **first path segment** of the branch name. diff --git a/.cursor/rules/story-kickoff.md b/.cursor/rules/story-kickoff.md index 0f31b2f..5b64f92 100644 --- a/.cursor/rules/story-kickoff.md +++ b/.cursor/rules/story-kickoff.md @@ -11,6 +11,7 @@ When the user starts work on a **Jira story** (e.g. issue key `NEON-2`, phrases - Fetch the issue when possible (e.g. Atlassian MCP `getJiraIssue`), or use a URL / pasted description the user provides. - Capture summary, description, acceptance criteria, and anything explicitly **out of scope**. +- **Hierarchy:** Expect **Epic → Story** (or Task/Bug). **Do not** add or assume a Jira **Feature** layer—**module / slice** grouping is **labels on the story** (see [Jira alignment](../../docs/decomposition/README.md#jira-alignment) in the decomposition README). ## 1a. Board status (To Do → In Progress) diff --git a/docs/decomposition/README.md b/docs/decomposition/README.md index 69898f7..1f4f08b 100644 --- a/docs/decomposition/README.md +++ b/docs/decomposition/README.md @@ -20,6 +20,12 @@ This workspace contains detailed planning artifacts derived from the finalized m 3. Use stable IDs (`E1`, `E1.M1`, etc.) for core game epics; use **`CT.M1`**-style IDs for [content tooling](tooling/internal_authoring.md) so tooling stays out of the E1–E9 sequence. 4. Every new slice must reference telemetry and validation where applicable. +## Jira alignment + +Engineering work is tracked as **Stories** (or **Tasks** / **Bugs** when appropriate) **under Epics**. **Do not** create Jira **Feature** issues for module- or slice-level grouping—that middle tier is not used. + +Express that grouping with **labels on the story** instead (for example the decomposition **module id** — `E1.M1`, `CT.M2`, etc. — or other labels the team maintains in Jira). The story still **belongs to the Epic** as today; labels carry what used to be “feature + labels on stories,” without a separate Feature work item. + ## Epic files (E1–E9, master plan) | Epic | Document | @@ -44,6 +50,6 @@ Template for new epics or major revisions: [epics/_epic_template.md](epics/_epic ## Next Actions -1. Expand slices into engineering tickets; keep module IDs aligned with the master plan. +1. Expand slices into **stories** under epics; tag **module / slice** scope with **labels** (not Jira Features). Keep module IDs aligned with the master plan. 2. Populate `modules/module_dependency_register.md` as contracts stabilize. 3. Refine `milestones/phase_execution_plan.md` with dates and owners when execution starts. diff --git a/docs/decomposition/modules/documentation_and_implementation_alignment.md b/docs/decomposition/modules/documentation_and_implementation_alignment.md index ff5f3d2..c5dbf2b 100644 --- a/docs/decomposition/modules/documentation_and_implementation_alignment.md +++ b/docs/decomposition/modules/documentation_and_implementation_alignment.md @@ -11,6 +11,7 @@ The [module dependency register](module_dependency_register.md) **Status** colum | **Register + module markdown** | Intent, dependencies, contracts, policies (authority, PvP, quests, ops). | | **Code + tests** | What actually runs; paths under `server/`, `client/`, etc. | | **Plans** | `docs/plans/` (e.g. NEON-* implementation plans) tie stories to acceptance criteria. | +| **Jira** | Stories under epics; **module grouping = labels** on the story (no Jira **Feature** issues). [Decomposition README — Jira alignment](../README.md#jira-alignment). | | **This doc’s tracking table** | Quick **inventory** of modules that have started implementation; expand as work lands. | ---