Back to browse
Ossature – Spec-driven code generation with LLMs

Ossature – Spec-driven code generation with LLMs

by beshrkayali·Mar 18, 2026·4 points·0 comments

AI Analysis

●●●BangerBig BrainSolve My Problem

Fix task 14 of 30 without restarting—Cursor's all-or-nothing approach can't do this.

Strengths
  • Spec validation catches structural errors before LLM invocation wastes tokens
  • Topologically ordered build plan tracks task dependencies automatically
  • Verification commands run after each task to catch failures early
Weaknesses
  • Requires writing detailed specs upfront which adds friction for quick prototypes
  • Smaller model support may struggle with complex architectural decisions
Target Audience

Developers using LLMs for code generation

Similar To

Cursor · Continue · Windsurf

Post Description

I've been working on Ossature, an open-source tool that takes a different approach to LLM code generation. Instead of prompting and hoping, you write specs describing what your software should do, Ossature breaks them into a build plan, and then executes it step by step with an LLM generating code under tight constraints.

The core idea: specs are the source of truth and the human stays in the loop. You review the plan before anything gets built. You can step through tasks one at a time or let it run and intervene on failures. When task 14 of 30 fails, you fix that task and keep going instead of starting over. When requirements change you update the spec and only the affected parts get rebuilt.

The workflow is validate -> audit -> build. Validate checks structure (no LLM). Audit sends specs to an LLM for review and generates the build plan. Build executes it task by task with verification after each step.

Works with Anthropic, OpenAI, Mistral, Google, etc. and local models through Ollama.

Python 3.14+, MIT licensed.

GitHub: https://github.com/ossature/ossature

Docs: https://docs.ossature.dev

Some examples: https://github.com/ossature/ossature-examples

This is v0.0.1. Right now it works best for greenfield projects. I want to support workflows against existing codebases but honestly I'm not sure yet what the right approach looks like there. If you have thoughts on that or anything else, open an issue or start a discussion on the repo.

Similar Projects

AI/ML●●Solid

Agenda Intel MD – schemas and CLI to audit LLM strategic-risk briefs

Schema-valid evidence packs for AI agents when generic evals miss domain nuance.

Niche GemBig Brain
vassilbek
101mo ago
AI/ML●●Solid

An adversarial reasoning engine for scientific progress

Catches LLMs cheating on evals with a 9-pattern catalog nobody else documents.

Big BrainNiche Gem
Sparckix
2015d ago

Math-spec-driven LLM skill for complex system specs

Math-spec approach for LLM-generated code, but lacks working examples and doesn't solve the reasoning-accuracy problem.

Big Brain
ben8t
104mo ago