dos-extract

dos-extract

Reverse-engineer a Design Ontology Spec from a repository. The product is two files: dos.yaml (the 12-section ontology) + decisions.md (why Topic, not TopicNode). This skill describes what a DOS is, the judgments that separate a real ontology from a scan dump, the primitive that does the mechanical scanning, the human seam, and the exit that certifies the result. It prescribes no step order — the engine sequences the work; what follows are the gaps and the gates.

The gap (why a scan is not an ontology)

A composite of three atoms: Knowledge (what a DOS is — the 12-section format, the code-vs-docs signal priority), Capability (the mechanical noun/verb scan — a primitive the engine otherwise mis-improvises), Judgment (the four classification calls below).

The load-bearing reason this is not free:

Code contains the current implementation choices, not the ontology that should exist. A naive "scan code → emit objects" pass freezes mistakes into the contract: a CommentCard React component becomes a CommentCard object — wrong twice (it is UI, and Card is presentation, not domain).

Deletion test: remove this skill and ask the engine to "extract a DOS from this repo." It greps nouns and emits a polluted ontology — UI elements and *Repository/*Service names promoted to objects, no ≤7 discipline, code vocabulary winning over the team's language. The gap is the semantic judgment, plus the knowledge of what a clean DOS looks like.

The world

• A DOS is a YAML contract in a fixed 12-section shape (assets/dos_template.yaml): meta, scope, objects, relationships, rules, composition, behaviors, bounded_contexts, agent_guidelines, anti_patterns, open_questions, evolution_log. It is the shared language between humans and AI agents — code converges to it, not it to code.
• Two signal sources, divergence is signal. Code shows what was built; docs show what the team talks about. When they agree, confidence is high. When they diverge (docs say Topic, code says Node), that divergence is itself evidence — and for ontology questions docs generally outrank code (code drifts under deadline; docs reflect intent). Full priority rules: references/methodology.md (code-vs-docs signal priority).
• Output is two files. dos.yaml (the ontology) + decisions.md (the audit trail — every non-trivial judgment traceable to one of the four by name).