Skip to content

lifecycles.md

Latest commit

 

History

History
70 lines (52 loc) · 2.53 KB

lifecycles.md

File metadata and controls

70 lines (52 loc) · 2.53 KB

Lifecycle flows

Visual overviews live on the README. This page has editable Mermaid diagrams for all paths, including Jira-tracked engineering.

Command prefixes: Claude Code uses /discover, /spec, … Cursor uses /sys-discover, /sys-spec, … (same workflows). SysPM PM commands: /pm-spec, /pm-epic, /pm-breakdown, /pm-sync.

Core lifecycle (repo-first)

The default path: map context when needed, lock intent with a spec and task breakdown, implement and prove quality in steps, then ship.

flowchart LR
    discover["Discover<br/>/discover"]
    define["Define<br/>/spec"]
    plan["Plan<br/>/plan"]
    build["Build<br/>/build"]
    verify["Verify<br/>/test"]
    review["Review<br/>/review"]
    ship["Ship<br/>/ship"]
    discover --> define --> plan --> build --> verify --> review --> ship
Loading

Jira-tracked lifecycle

For work anchored to a Jira story: grounded spec and story-scoped plan (/jira-spec, /jira-plan), then /jira-sync drafts sync.md under jira-spec/{story-id}/ (Current vs Proposed for story + tasks). Apply to Jira only after explicit approval. Then /build. Verify and review match the core path; /jira-ship adds launch + Jira visibility.

flowchart LR
    discover["Discover<br/>/discover"]
    jspec["Define<br/>/jira-spec"]
    jplan["Plan<br/>/jira-plan"]
    jsync["Sync board<br/>/jira-sync"]
    build["Build<br/>/build"]
    test["Verify<br/>/test"]
    review["Review<br/>/review"]
    jship["Ship<br/>/jira-ship"]
    discover --> jspec --> jplan --> jsync --> build --> test --> review --> jship
Loading

/discover first is optional in both engineering flows — skip when brownfield context is unnecessary.

SysPM PM lifecycle

For PM-first initiative shaping: create a PRD, convert to epic, break into T### work items, then sync to Jira. Engineering can then proceed in the Jira story flow above.

flowchart LR
    pmspec["Define PRD<br/>/pm-spec"]
    pmepic["Create epic<br/>/pm-epic"]
    pmbreak["Breakdown<br/>/pm-breakdown"]
    pmsync["Sync board<br/>/pm-sync"]
    handoff["Handoff to engineering Jira flow"]
    pmspec --> pmepic --> pmbreak --> pmsync --> handoff
Loading

When to use which path

Path Use when
Core Repo-first work; specs and tasks live in the repository
Jira-tracked Story is the source of truth in Jira; board sync before build
SysPM PM shapes PRD → epic → work items before engineering picks up stories