build: improved the way the project rules are disseminated

2026-04-12 22:33:34 -04:00
parent 56a430d31f
commit d5446081e3
2 changed files with 3 additions and 3 deletions
@@ -157,5 +157,5 @@ Fixes applied:
 2. **Read all comments and reviews.** For PRs, the formal reviews and review comments are essential context — they may explain why labels or states are in a particular condition.
 3. **Comment before modifying.** Always explain what you're changing and why.
 4. **PR labels sync to linked issue.** Priority, Type, MoSCoW, and milestone always flow from the issue to the PR, not the other way.
-5. **Never create labels.** Use `forgejo-label-manager` to apply existing labels.
+5. **Always use existing labels.** Use `forgejo-label-manager` to apply existing labels.
 6. **Always post the `[GROOMED]` marker** at the end so the supervisor knows this item was processed.
@@ -169,11 +169,11 @@ If any of the files from Step 2 are missing, invoke `project-bootstrapper` with

 ### Step 4: Load Reference Materials and Prepare Supervisor Briefings

-Before launching supervisors, build a customized briefing for each one so that every supervisor starts with full knowledge of the development rules and current system state. This avoids each supervisor independently discovering the same information, saving startup time and tokens.
+Before launching supervisors, build a customized, highly detailed, complete, and pedantically thurough, briefing for each one so that every supervisor starts with full knowledge of the development rules and current system state in full detail. This avoids each supervisor independently discovering the same information, saving startup time and tokens.

 **Gather the source material** by invoking these subagents:

-1. Invoke `ref-reader` to load and summarize `CONTRIBUTING.md` and `docs/specification.md`. The CONTRIBUTING.md content is especially critical — it contains the development rules, testing philosophy, commit standards, PR requirements, quality gates, label system, and issue format that every agent must follow.
+1. Invoke `ref-reader` to load and summarize `CONTRIBUTING.md` and `docs/specification.md`. The CONTRIBUTING.md content is especially critical — it contains the development rules, testing philosophy, commit standards, PR requirements, quality gates, label system, and issue format that every agent must follow. When you call ref_reader to produce the summaries that will be passed to each supervisor, make sure they produce a highly targeted, and high detailed and complete summary for each of the supervisors.

 2. Invoke `automation-tracking-manager` with `READ_ANNOUNCEMENTS` to retrieve all open announcement issues across all agent prefixes. These contain active conditions the system is dealing with (degraded capacity, quality gate violations, blocking issues, etc.).