Normalisering af alle 39 custom knowledge-filer til READ-kontraktens skema (validate_frontmatter.py + Test-KnowledgeIndex.ps1 begge groenne): - R01/R02: 28 filer manglede frontmatter eller brugte aeldre skemaer (title/category/severity/rule-id m.fl.) - alle har nu praecis de 6 kraevede noegler; keywords haandskrevet pr. fil da de driver worklist-selektionen i INDEX/knowledge-index - R09: manglende Description-sektion - regel-agtige foersteoverskrifter (Core Rule/Rule/Regel/Core Principle) omdoebt, eller sektion indsat efter titlen hvor intro-tekst fandtes - R10: fenced code blocks konverteret til 4-space indrykkede blokke i alle filer (indhold uaendret) - R11: 4 filer over 100 linjer fortaettet redaktionelt uden semantisk tab (ai-eval-scores 143->100, git-lifecycle 121->97, permission-sets 113->99, test-feature-scenario-tags 105->91) - R05: AL0197->al0197, add_repo->add-repo; keyword-lister trimmet til maks 10 Ingen regler er fjernet eller aendret i betydning - kun form. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.2 KiB
| bc-version | domain | keywords | technologies | countries | application-area | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
architecture |
|
|
|
|
bc-version: [all] domain: architecture keywords: [claude-md, agents, visibility, setup, mode-b, curabis-standard] technologies: [al] countries: [w1] application-area: [all]
Description
When new agents are added to BCQuality and installed via Mode B update, they
are written to .github/.agents/ but CLAUDE.md is never touched (Mode B
preserves project-specific files). This means newly installed agents are
invisible to Claude — it will not invoke them because it does not know they exist.
This gap was observed when four court agents (court, lincoln, aurelius, munger) were installed via Mode B but remained uncallable until the developer asked directly. Claude had no way to discover them proactively.
Rule
After any installation or update of agent files in .github/.agents/, Claude
must verify that every .agent.md file in that directory is referenced in
CLAUDE.md. Any agent not listed in CLAUDE.md must be flagged to the developer
with a proposed addition before the session continues.
What NOT to do
- Do not silently install agents without checking CLAUDE.md coverage
- Do not assume that because a file exists in
.github/.agents/it is known to Claude - Do not wait until session end to flag the discrepancy — flag it immediately after install
- Do not add agents to CLAUDE.md without showing the developer the proposed wording first
Signal to watch for
After running Mode B (or any agent install), compare:
Get-ChildItem .github/.agents/*.agent.md | Select-Object -ExpandProperty BaseName
against the agent references in CLAUDE.md. Any filename present in the directory but absent from CLAUDE.md is a gap that must be surfaced.
Message to developer
When a gap is found, output exactly this before continuing:
⚠️ Ny agent installeret men ikke refereret i CLAUDE.md:
- <agent-navn>.agent.md
Claude kan ikke kalde denne agent medmindre den tilføjes til CLAUDE.md.
Vil du have mig til at tilføje den nu?
Do not continue with other activity until the developer has responded.