Skip to main content

Example Initiative

This folder demonstrates the layout every initiative follows under the depth-2 <team>/<initiative>/ structure. Copy it (or just its structure) when starting a new initiative under your team.

Structure​

  • prds/ — Product Requirements Documents (see the example PRD).
  • rfcs/ — technical design proposals (RFCs).
  • tests/ — E2E / acceptance test specs that trace back to PRD acceptance criteria (see the example test spec).
  • delivery/ — TPM program-management docs: a timeline.md, periodic status/ reports (delivery health lives in a health: field, never the linter's status:), and ADR-style decisions/. Not read by Jira sync or the e2e runner.

Scope Changes​

Engineering surfaces this initiative touches, aggregated across its PRDs. Pick from the controlled vocabulary — Backend · Frontend · Mobile · Infra · Data · Design · Docs · None — and add a one-line note per surface. Keep this list in sync with the scope_changes frontmatter field above; each PRD narrows it to the surfaces that PRD changes.

  • Backend — the example initiative's docs pipeline (illustrative only).
  • Frontend — the rendered Docusaurus page for this initiative (illustrative only).

QA Lane​

Whether this initiative needs a human QA gate. Lane B (illustrative) — kept as the safe default until the qa-lane-advisor skill classifies it. Lane A means it ships on automation with no manual gate (no Lane-B trigger — not money-critical, security, real-time, or out-of-reach — and a 100% E2E-covered, spec-mapped entry bar). The decision rules live in .claude/reference/qa-lanes.md; the methodology is in the system repo's QA-LANES.md.

  • Lane B — illustrative default; reclassify with the advisor and bump qa_lane_as_of.

The README.md is the initiative landing page; the linter requires title, status, and dri in its frontmatter. team, target_quarter, and scope_changes are advisory fields repeated onto each PRD/RFC (each PRD's scope_changes is the subset of surfaces that PRD changes). qa_lane is advisory too, but — unlike those — it is an initiative-level classification that stays on this README.md only; it is never repeated onto a PRD/RFC.