You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b973563
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: dev/build/ProjectInstructions/TEAM_START_COMMANDS.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,13 @@ Non-Owner team PRs use Stacked PR workstreams by default. A non-Owner team PR ma
23
23
24
24
Use `dev/build/ProjectInstructions/` as the only active Project Instructions source.
25
25
Read `dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` before implementation.
26
+
Read `dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md` during startup.
27
+
28
+
`BACKLOG_MASTER.md` is the authoritative source for assigned product work. `admin/tool-votes.html` is the Tool Votes/Admin Owner priority signal source for tool demand and Owner/Admin review; it informs backlog priority but does not replace the backlog.
29
+
30
+
Team startup must display the Team Assignment table defined in `dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`.
31
+
32
+
Codex must not invent work from conversation memory when `BACKLOG_MASTER.md` has a matching product area.
26
33
27
34
Branch Lifecycle (Canonical):
28
35
- Follow `dev/build/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` for START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock.
@@ -45,10 +52,12 @@ Ready-to-copy command:
45
52
OWNER override approved: Start Alfa from the ProjectInstructions release gate.
Tool demand and Owner/Admin priority signal source:
36
+
37
+
```text
38
+
admin/tool-votes.html
39
+
```
40
+
41
+
The Tool Votes/Admin Owner planning surface informs backlog priority, Owner/Admin review, tool demand, and reprioritization. It does not replace `BACKLOG_MASTER.md` as the authoritative assigned-work source.
42
+
29
43
Every active team owns an active backlog when it has assigned work.
30
44
31
45
Each backlog item must track:
32
46
33
47
- name
34
48
- description
49
+
- product area
50
+
- status
35
51
- current completion percentage
52
+
- active PR, when one exists
53
+
- next milestone
36
54
- remaining work
37
55
- blocking dependencies
38
56
- owning team
57
+
- source or reference
39
58
40
59
Completion percentages are updated:
41
60
42
61
- at SOD
62
+
- when work changes status
43
63
- after every accepted PR
44
64
- at EOD
45
65
46
66
The backlog is the authoritative source for determining the next logical PRs.
47
67
48
68
If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision.
49
69
70
+
Codex must not invent assigned product work from conversation memory when `BACKLOG_MASTER.md` has a matching product area.
71
+
72
+
Teams must update backlog status and percent complete when work changes status.
73
+
74
+
Owner must update backlog status, completion percentage, and Tool Votes/Admin Owner status when assigning, reprioritizing, completing, or deferring work.
75
+
50
76
When the Product Owner provides a completed PR ZIP, ChatGPT must review that ZIP, update the active team backlog and completion percentages, and recommend the next logical PRs needed to keep moving toward a Product Owner testable outcome.
2. Locate its assigned team section and assigned product areas.
84
+
3. Read the Tool Votes/Admin Owner priority signal source at `admin/tool-votes.html` when the work involves tool demand, tool ordering, or Owner/Admin prioritization.
85
+
4. Display assignments as a table grouped by Team, then Product Area.
86
+
5. Include Team, Product Area, Status, Percent Complete, Active PR, Next Milestone, and Source / Reference for every assignment row.
If the task is not represented in `BACKLOG_MASTER.md` or the Tool Votes/Admin Owner planning source, Codex must flag the missing representation and ask OWNER whether to add or update the backlog before continuing.
108
+
52
109
## Start Of Day Team Briefing
53
110
54
111
When a team is assigned, ChatGPT/Codex must provide this briefing before implementation begins:
@@ -65,6 +122,18 @@ When a team is assigned, ChatGPT/Codex must provide this briefing before impleme
65
122
66
123
This briefing is required before implementation begins.
67
124
125
+
The briefing must include the Team Assignment startup output defined above.
126
+
127
+
## Startup Hard Stops
128
+
129
+
STOP before implementation when:
130
+
131
+
-`dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md` cannot be found.
132
+
- the assigned team cannot be found in the backlog, unless OWNER explicitly provided a one-off task.
133
+
- the requested product-area task is not represented in the backlog or Tool Votes/Admin Owner planning source, until OWNER confirms whether to update the backlog.
134
+
135
+
If `admin/tool-votes.html` cannot be found, document the missing priority signal source and recommend `admin/tool-votes.html` as the canonical path instead of inventing a replacement.
Copy file name to clipboardExpand all lines: dev/build/ProjectInstructions/addendums/team_start_and_release.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,13 @@ Before a team starts, validate:
19
19
-`main...origin/main` is `0 0`
20
20
-`HEAD` SHA matches published EOD SHA
21
21
- active assignment is selected or confirmed by OWNER
22
+
-`dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md` is loaded as the authoritative assigned-work source
23
+
-`admin/tool-votes.html` is located as the Tool Votes/Admin Owner priority signal source
22
24
- assigned team uses the canonical Owner plus military team-name set
23
25
- work remains with the assigned team until complete or OWNER reassignment
24
26
- the team's previous PR is Closed, unless OWNER documented an explicit stacked PR chain
25
27
26
-
Before implementation begins, ChatGPT/Codex must provide the SOD briefing defined in `dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`.
28
+
Before implementation begins, ChatGPT/Codex must provide the SOD briefing and Team Assignment table defined in `dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`.
This file is the authoritative source for assigned product work.
8
+
9
+
This document is updated as work status changes, including Owner assignment, reprioritization, completion, deferral, accepted PRs, SOD review, and EOD review.
10
+
11
+
Backlog content must be organized by Team, then Product Area. Existing roadmap phase sections must preserve explicit team/product-area ownership until they are normalized into the Team/Product Area grouping.
12
+
13
+
Each product area must include status and percent complete.
14
+
7
15
Every active team owns an active backlog when it has assigned work.
8
16
9
17
Backlog entries in this file follow the canonical field list, including:
10
18
11
19
- Name
12
20
- Description
21
+
- Product area
22
+
- Status
13
23
- Current completion percentage
24
+
- Active PR, when one exists
25
+
- Next milestone
14
26
- Remaining work
15
27
- Blocking dependencies
16
28
- Owning team
29
+
- Source or reference
17
30
18
31
Completion percentages are updated at SOD, after every accepted PR, and at EOD.
Start of Day may recommend the next execution phase, but it must not execute that phase.
69
78
70
79
Start of Day must satisfy the Codex Completion Contract in `dev/build/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md`. Because Start of Day is read-only discovery, its ZIP outcome is review-only unless another outcome is explicitly documented.
0 commit comments