blog post - modularity in spec files

The import directive

Notice the markdown extension -- front matter at the top of main.cs.md:

---
import storage.cs.md
---

This tells CodeSpeak that main.cs.md depends on storage.cs.md. When building main.cs.md, CodeSpeak will first build the storage spec, and then build the main spec with full knowledge of what storage provides.

You can import multiple specs, and imports are transitive — if A imports B and B imports C, CodeSpeak will build all three in the right order.
......
transitive dependency resolution
......
app specification will be done with agents and markdown
...
YAML frontmatter enables dependency-aware specifications

That's it — one line changed. The main spec stays exactly the same, because it doesn't care how memos are stored. It only cares that storage exists and provides certain capabilities. This is the payoff of splitting specs: changes to one concern don't ripple into unrelated specs, making them easier to review and reason about.
...
dim - review ease -- higher
...
code-associated specification file