Context
Running AgentReady on the Kagenti repos, we noticed the ADR check (architecture_decisions) only accepts four directory paths.
Limited directory paths
The check currently accepts: docs/adr/, .adr/, adr/, docs/decisions/. Some projects use specs/ or docs/specs/ for design documents that serve the same purpose. AgentReady itself has a specs/ directory. Projects following the MADR format sometimes use docs/architecture/ or docs/design/.
Proposal: Add specs/, docs/specs/, docs/architecture/, and docs/design/ to the accepted paths. Alternatively, make the directory path configurable via .agentready-config.yaml so projects can specify where their architectural decisions live.
Why this matters
Projects that maintain design documents outside the four hardcoded paths get a false failure on this check. The content exists, the check just doesn't look in the right place.
Context
Running AgentReady on the Kagenti repos, we noticed the ADR check (
architecture_decisions) only accepts four directory paths.Limited directory paths
The check currently accepts:
docs/adr/,.adr/,adr/,docs/decisions/. Some projects usespecs/ordocs/specs/for design documents that serve the same purpose. AgentReady itself has aspecs/directory. Projects following the MADR format sometimes usedocs/architecture/ordocs/design/.Proposal: Add
specs/,docs/specs/,docs/architecture/, anddocs/design/to the accepted paths. Alternatively, make the directory path configurable via.agentready-config.yamlso projects can specify where their architectural decisions live.Why this matters
Projects that maintain design documents outside the four hardcoded paths get a false failure on this check. The content exists, the check just doesn't look in the right place.