This flow describes the stable path from a new requirement to the implemented change in the correct repo.

Purpose

  • keep scope, work docs, sources, and repo change aligned

Trigger

  • new product, docs, skill, or operations requirement

Participating systems

Inputs and outputs

  • Inputs:
    • requirement, problem, or change request
  • Outputs:
    • Jira issue, public work doc, repo change, commit

Flow

  1. check or create the matching Jira issue
  2. create or update the public work doc under work/jira/
  3. clarify sources and target location
  4. change the correct repo or several clearly separated repos
  5. verify, commit, and integrate

Handovers

  • Jira -> public work doc
  • work doc -> repo change
  • repo change -> public explanation or closure picture

Boundaries and non-goals

  • not a replacement for detailed runbooks
  • no mixed commits across repos

Sources