RunLogosRunLogos
Coming Soon
Open Source Methodology

OpenLogos Defines the Standards. RunLogos Makes Them Land Better.

OpenLogos is a free, open-source AI engineering methodology. It encodes 40+ years of proven practices — BDD, TDD, DDD, Stage-Gate — as AI-executable Skills that work with any AI coding tool. RunLogos is the professional desktop application that brings every artifact the methodology produces to life.

openlogos.aiGitHub
OpenLogos website homepage
Why two products?
OpenLogos
The Methodology
Open Source · Apache 2.0 · Free

A structured AI engineering methodology encoded as Markdown Skills. Works standalone with any AI coding tool — Claude Code, Cursor, OpenCode, GitHub Copilot, and more.

13 built-in AI Skills covering the full lifecycle
CLI tool: openlogos init / verify / change
Formal specs: workflow, project structure, test results
Platform-agnostic — any AI tool that reads Markdown
RunLogos
RunLogos
The Desktop App
Community Free · Pro $49 one-time

The best-practice implementation of OpenLogos. Visualize, edit, orchestrate, and debug every artifact the methodology produces — all in one native desktop application.

Visual editors for Markdown, OpenAPI, and DB schemas
API orchestration runner with request/response inspector
Comment-to-Prompt for precise AI collaboration
Change management & test result dashboard
This relationship follows well-established industry precedents:
OpenAPISwaggerHub
KubernetesOpenShift
Scrum / AgileJira / Linear
GraphQLApollo Studio
The OpenLogos Spec Chain

OpenLogos encodes the Why → What → How progression as AI-executable Skills. Every layer derives from the one before it — producing a fully traceable chain from requirements to passing tests.

WHY
Phase 1
Requirements
User persona & pain points
Scenario identification (S01, S02…)
GIVEN/WHEN/THEN acceptance criteria
Scope boundaries ("Won't do" list)
prd-writer
WHAT
Phase 2
Product Design
Information architecture
Feature specifications per scenario
HTML prototype generation
UI-level acceptance criteria
product-designer
HOW
Phase 3
Implementation
Architecture & tech stack
Sequence diagrams → APIs emerge
OpenAPI YAML + DB schema (DDL)
Test cases (before code!) → Code → Verify
6 Skills
How they work together

OpenLogos and RunLogos form a closed-loop cycle. The methodology drives what to build; the desktop app makes everything it produces visible, editable, and testable.

01
Methodology-Driven in Your AI Tool
OpenLogos

Use OpenLogos Skills in Claude Code, Cursor, or any AI coding tool to execute the full Requirements → Design → Code workflow. The AI reads AGENTS.md and knows exactly which phase to work on and which Skill to load.

Claude Code running an OpenLogos Skill in terminal
02
Visualize & Edit Every Artifact in RunLogos
RunLogos

All AI-generated documents — PRD Markdown, HTML prototypes, sequence diagrams, OpenAPI specs, DB schemas, test cases, change proposals — are rendered visually in RunLogos with full editing support.

RunLogos document viewer showing PRD / OpenAPI editor
03
Orchestrate & Test API Scenarios
RunLogos

Run the AI-written API orchestration test scenarios directly inside RunLogos. Inspect every request and response in detail. The scenario runner validates your business flows against the OpenLogos Spec Chain — no external test harness needed.

RunLogos API orchestration runner with request/response inspector
04
Comment-to-Prompt for Precise AI Feedback
RunLogos

Highlight any text in a RunLogos document, leave inline comments, then generate a structured AI prompt from those comments. Turns vague review notes into precise instructions — dramatically improving how you communicate with the AI coding tool.

RunLogos comment panel → generated AI prompt
05
Verify with openlogos verify
OpenLogos

Run the CLI verification command to produce a three-layer traceability report: pass rate, design-time coverage (every defined test case was executed), and AC traceability (requirements → test cases → results). You ship with proof, not hope.

openlogos verify output / RunLogos acceptance report dashboard
OpenLogos core principles
WHY → WHAT → HOW

Every project moves through three layers. Requirements come before design; design comes before code. AI never guesses when context is fully defined.

Scenario + Test-First

A single scenario ID travels through all phases. Test cases are designed before code is generated. openlogos verify produces a three-layer traceability report.

Documents as Context

Every decision lives in a Markdown file. The same documents → the same context → consistent AI output. Reviewable, reproducible, and cumulative across the entire team.

Harness Engineering

AGENTS.md auto-detects the current phase, loads the right Skill, and enforces rules like "never write code without design docs." AI does the heavy lifting; you maintain control.

Built on 40+ years of proven theory

OpenLogos is not a new framework invented from scratch — it maps established software engineering methodologies onto AI-native execution.

BDD
2006
Dan North

Phase 1 GIVEN/WHEN/THEN acceptance criteria

TDD
2003
Kent Beck

Phase 3 Step 3 test-first design, openlogos verify

DDD
2003
Eric Evans

Architecture, scenario modeling, ubiquitous language

Stage-Gate
1986
Robert Cooper

Three-layer progression gates, Gate 3.5

Docs-as-Code
2014
Community

Documents as Context, logos/ directory structure

Executable Methodology
AI-native
OpenLogos

AI Skills (SKILL.md), AGENTS.md auto-detection

Start with the methodology. Amplify with the app.

OpenLogos is free and works with any AI coding tool today. RunLogos adds the visual layer that makes every artifact the methodology produces easier to review, edit, and act on.

Get OpenLogos FreeGet RunLogos Pro — $49