Agent Skills

Dewey — Classifier

Assigns taxonomy level (L1-L6) to each document, enforces required documents per project level.

Document Hierarchy (L1–L6)

Level Type Examples
L1 Contracts contracts/openapi/*.yaml, contracts/asyncapi/*.yaml
L2 Product Canon docs/VISION.md, docs/PRD.md, docs/ROADMAP.md, docs/FEATURES.md
L3 Engineering Canon docs/ARCHITECTURE.md, docs/ADR/, docs/SAGA/, docs/TEST_CASES.md
L4 Derived docs/REFERENCE.md, docs/DEV_GUIDE.md, docs/STATUS.md
L5 Artifacts Generated files (API docs, changelogs, diagrams)
L6 Auxiliary README.md, CONTRIBUTING.md, LICENSE, templates

What it does

Usage

# Via Chronos orchestrator
chronos --path . --preset standard

# Direct invocation
python -m chronos.agents.dewey --path .

Output Format

[warning] missing: Required L2 document missing — docs/ROADMAP.md
[info] classified: docs/ARCHITECTURE.md → L3 Engineering Canon
[info] project_level: L2 (Product Canon) — 3/4 required docs present

Required Documents per Level

Level Required
L1 At least 1 contract file (OpenAPI/AsyncAPI/JSON Schema)
L2 VISION.md, PRD.md, ROADMAP.md
L3 ARCHITECTURE.md, ADR/ directory

Triggers

Integration

Loaded by Chronos as part of standard and full presets.

Boundaries

Procedure and output contract

Classify by normalized repository-relative path, report the matched rule, and show the detected maturity level before checking required documents. Required-document findings are warnings until the project declares a stricter policy. Unknown files must be reported as unknown rather than forced into a taxonomy level.

Verification

A useful report includes every document’s classification, the rule or pattern that matched it, required documents considered, and a deterministic summary. Review false positives for custom repository layouts before creating files.