The problem I want to solve is simple: when we work with programming agents, we often end up creating too many .md files: requirements, architecture, decisions, notes, prompts, issues… Too much Markdown. Not enough structured truth. And the agent ends up navigating scattered context, outdated documentation, and specifications that are hard to validate. Before: ❌ Markdown everywhere ❌ Duplicated or outdated requirements ❌ Long prompts to explain the same thing again ❌ Agents without a clear source of truth ❌ Manual verification to check whether the result matches the intent With Specra: ✅ A compact contract in .scl.md ✅ Intent, entities, operations, expectations, constraints, and targets in one format ✅ Compact artifacts for agents ✅ Less noise, more useful context ✅ Verification against observed results The idea is not to write more documentation. The idea is to replace unstructured Markdown with contracts that agents can understand, use, and verify. Specra is contract-driven AI coding and verification. You write a compact spec, the agent implements against it, and then you can verify the observed behavior in a repeatable loop. Website: https://davidnazareno.github.io/specra-lang/ Repo: https://github.com/DavidNazareno/specra-lang I’d love feedback from people working with coding agents, SDD, specs, tests, or workflows with Codex / Claude Code / OpenCode. What do you think of this approach? submitted by /u/Feeling-Stop-897
Originally posted by u/Feeling-Stop-897 on r/ArtificialInteligence