Skip to content

chore(specs): write M101 FRs (STE-375/376/377) + plan#36

Open
nesquikm wants to merge 1 commit into
mainfrom
feat/ste-375-jira-milestone-as-epic
Open

chore(specs): write M101 FRs (STE-375/376/377) + plan#36
nesquikm wants to merge 1 commit into
mainfrom
feat/ste-375-jira-milestone-as-epic

Conversation

@nesquikm

Copy link
Copy Markdown
Owner

Summary

  • Specs for M101 "Lineage" — give Jira milestones a first-class identity: each milestone becomes a Jira Epic owning its FR Tasks via parent, identified by M_<epic-key> (collision-free via the unique tracker key, no scan-to-allocate, self-describing). Union grammar accepts M_<key> alongside legacy M<N>. Jira-only; Linear + mode:none keep sequential M<N>.
  • Three FRs (build order STE-376 → STE-375 → STE-377): STE-376 M_<epic-key> union grammar, STE-375 Jira Epic milestone object, STE-377 Epic-first allocation in /spec-write.
  • Spec-only / parked — FRs are in Backlog, not yet implemented. Design approved via /brainstorm 2026-07-09; chosen over key-rank-M93 for the self-describing/no-mapping model.

Test plan

  • /implement M101 (start STE-376) — implementation + bun test full gate + /gate-check GREEN
  • /spec-review (or /tdd AUDIT) traces all 15 ACs to file:line + test:line
  • /ship-milestone M101 → release v2.44.0 "Lineage"

Follow-up: implement M101 (parked for later).

M101 "Lineage" — Jira milestone-as-Epic identity. Design approved via
/brainstorm 2026-07-09.

Refs: STE-375, STE-376, STE-377
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant