Repository navigation
/pr-review and /build gather standards from CLAUDE.md and every file it points at #648
Closed as not planned
Description
Question
How do /pr-review and /build gather a repository's standards from CLAUDE.md and every file it points at?
Practice Packs must stack decided that a Practice Pack reaches a Box run through its own managed block in the Consumer's CLAUDE.md. #547 found that /pr-review's Standards axis reads four root files only, while /build reads anything that documents how code is written. The maintainer wants one rule for every Consumer.
Split out of #520 on 2026-10-21. Name the Box behaviour, not a step number, because #629 may replace the review node.
Order
- It waits for Practice Packs must stack: /setup replaces .archon/methods/ wholesale, and the override tier was deleted #520's criterion 1, the measurement of whether a node follows a pointer in
CLAUDE.md. If the node does not follow it, this ticket has no basis. - It edits Box files, so it waits for #502, as #542 orders, and its order against #521 is decided at grilling.
- The diagrams for the two pipelines under
apps/claude-code/unic-archon-dlc/docs/architecture/go stale with it.
Activity
fix(unic-archon-dlc): close Step 7 marker gaps and correct ADR-0038
orioltf commentedon Nov 3, 2026
unic-archon-dlc is frozen. This question carries over to adlc, its successor, as input for adlc's map (internal Jira APD-3). Nothing more happens on it in this repository.