Grey.ooo/agent-standards
Watch
2
0
Fork
You've already forked agent-standards
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Watch CI with Monitor, not ScheduleWakeup; keep multi-phase features to one PR #34

Merged
geusebio merged 1 commit from docs/monitor-over-schedulewakeup-and-single-pr-multiphase into main 2026-08-26 12:46:56 +00:00
Conversation 0 Commits 1 Files changed 1 +14 -14
geusebio commented 2026-08-26 12:46:09 +00:00
Owner
Copy link

Two working-agreement corrections, requested by a project maintainer:

  1. CI/wait watching reverts to Monitor. The previous guidance (drive waits through
    /loop dynamic mode + ScheduleWakeup, no Monitor armed, to avoid the session reading
    as "busy") is replaced with watching via Monitor in the same turn — accepted "busy" state
    in exchange for one continuous log of the wait instead of a wait split across wakeups.
  2. Multi-phase features stay in one PR. New bullet under Pull requests: splitting a
    feature's own implementation phases (schema, then service, then UI) into separate PRs is
    discouraged by default — intermediate commits mark phase boundaries, not intermediate PRs.
    Split only for a concrete reason (independent review/deploy timing, or diff size).

Docs-only change — no code, no CI in this repo to run.

Two working-agreement corrections, requested by a project maintainer: 1. **CI/wait watching reverts to `Monitor`.** The previous guidance (drive waits through `/loop` dynamic mode + `ScheduleWakeup`, no `Monitor` armed, to avoid the session reading as "busy") is replaced with watching via `Monitor` in the same turn — accepted "busy" state in exchange for one continuous log of the wait instead of a wait split across wakeups. 2. **Multi-phase features stay in one PR.** New bullet under Pull requests: splitting a feature's own implementation phases (schema, then service, then UI) into separate PRs is discouraged by default — intermediate commits mark phase boundaries, not intermediate PRs. Split only for a concrete reason (independent review/deploy timing, or diff size). Docs-only change — no code, no CI in this repo to run.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/agent-standards!34
No description provided.