RunLogosThe Spec Chain
The Spec Chain is the core concept behind RunLogos: a sequence of 9 phases where each phase's output becomes the next phase's input. AI never guesses — it reads explicit, structured context at every step.
Requirements → Prototype → Scenarios → API → Schema → Tests → Code → Verify → Change
01 02 03 04 05 06 07 08 09
Why it works
When you hand AI a complete Spec Chain, it knows:
- What to build (requirements + prototype)
- How the system behaves (scenarios)
- What the interface looks like (API contracts)
- Where data lives (DB schema)
- What "correct" means (test cases)
This eliminates the #1 cause of AI coding failures: missing context.
The 9 phases
01 · Requirements
A built-in Skill guides a structured conversation. Output: requirements.md with personas, pain points, scenario IDs (S01, S02…), and acceptance criteria.
02 · Product Design
The Design Skill reads requirements and generates an HTML prototype. Preview it, add inline comments, iterate.
03 · Scenario Mapping
The Scenario Skill reads the prototype and generates sequence diagrams — which actor calls which API, in what order, with what edge cases.
04 · API Design
The API Skill reads scenarios and generates a complete OpenAPI specification. Every endpoint traces back to a scenario step.
05 · Database Design
The Schema Skill reads the API and derives the data model. Visual table editor with DDL export for SQLite, PostgreSQL, or MySQL.
06 · Test Design
The Test Skill reads scenarios and writes unit and integration test cases — before any code exists.
07 · Code Generation
Hand the full Spec Chain to AI in one pass. No hallucinated endpoints. No guessed table names. No missing edge cases.
08 · Verification
Run openlogos verify. Every requirement traces to a test case, every test case to a result. Ship with proof.
09 · Change Proposals
After launch, every change starts with a Delta proposal — not a direct code edit. Impact analysis, affected artifacts, structured propagation.