Skip to content

Story tracking structure: stable IDs, workflow, and features.md rewrite#1452

Merged
sven1103 merged 1 commit into
developmentfrom
feature/story-tracking-structure
Jun 16, 2026
Merged

Story tracking structure: stable IDs, workflow, and features.md rewrite#1452
sven1103 merged 1 commit into
developmentfrom
feature/story-tracking-structure

Conversation

@sven1103-agent

Copy link
Copy Markdown
Collaborator

Summary

Establishes a stable story tracking structure for the data manager project. Introduces Story IDs, a documented story lifecycle workflow, and migrates existing immunopeptidomics stories into docs/features.md as the stakeholder-facing source of truth.

Changes

docs/features.md — rewritten

  • Story ID schema documented: FEAT-<SLUG>-<NN>
  • All 5 immunopeptidomics stories migrated with full narrative, acceptance criteria, stable IDs, and status
  • Task section removed — tasks remain GitHub-only (implementation-level)

AGENTS.md — updated

  • Governance hierarchy now reflects docs/features.md as the story source of truth
  • New Story ID Schema section (§0) with rules and examples
  • New Story Lifecycle section (§0) documenting the draft → approved → implement flow
  • Updated task rules to reference stories by stable ID
  • New "Creating Stories" section (§11) for agent delegation guidance
  • Key Files Quick Reference now includes docs/features.md

GitHub issues — all 10 issues updated (already applied)

Story issues (#1428#1432):

Issue Stable ID
#1428 FEAT-IP-MEAS-01
#1429 FEAT-IP-MEAS-02
#1430 FEAT-IP-MEAS-03
#1431 FEAT-IP-MEAS-04
#1432 FEAT-IP-MEAS-05

Task issues (#1413#1417): Parent Story field updated to reference stories by stable ID (e.g. FEAT-IP-MEAS-01 (#1428)).

IT tasks (#1437#1441): Comments added marking them as superseded/skipped for this feature.

Story ID Schema

FEAT-<SLUG>-<NN>
  • SLUG: abbreviated identifier derived from parent Feature (e.g., IP-MEAS for FEAT-IMMUNOPEPTIDOMICS-MEASUREMENT)
  • NN: sequential number, zero-padded (e.g., 01, 02)

Story Lifecycle

  1. Draft — discussion/refinement in SharePoint Word doc (no stable ID, not in features.md)
  2. Approved — stable ID assigned, story written into docs/features.md, GitHub issue updated
  3. Implementation — Tasks reference the story by stable ID, not by GitHub issue number

What to review

  • docs/features.md — story content, acceptance criteria, IDs, status
  • AGENTS.md — new Story ID Schema, Story Lifecycle, and Creating Stories sections

- Rewrite docs/features.md: story ID schema (FEAT-<SLUG>-<NN>),
  full story content with narrative and acceptance criteria,
  task section removed (tasks are GitHub-only)
- Update AGENTS.md: Story ID Schema section, Story Lifecycle
  workflow, Creating Stories section, Key Files Quick Reference
- Migrate FEAT-IP-MEAS-01 through FEAT-IP-MEAS-05 with complete
  story content from existing GitHub issues #1428-#1432
@sven1103-agent sven1103-agent requested a review from a team as a code owner June 15, 2026 11:26
@sonarqubecloud

Copy link
Copy Markdown

@sven1103 sven1103 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After talking to @Steffengreiner we go with this suggestion.

@sven1103 sven1103 merged commit 693ab6d into development Jun 16, 2026
10 checks passed
@sven1103 sven1103 deleted the feature/story-tracking-structure branch June 16, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants