Write down what you are building once, in markdown your coding agent reads before it touches the code, with a decision log that only a person confirms. Your agent shouldn’t start from zero every session. For solo developers and founders shipping with Claude Code, Codex, or Cursor.
Free for macOS, Windows, and Linux. No account, no subscription.
Sound familiar?
A choice the team ruled out on purpose comes back in the next session, written with total confidence, and nobody notices until it costs something.
You re-explain the project, paste the old plan, and grow CLAUDE.md a little longer, until nobody remembers where its rules came from.
A spec kit writes a long document for every change, often by the agent itself. Months later the specs and the code disagree, and a stale doc is worse than none.
How it fits
Install the software framework and every feature gets one file: why it exists, what it promises, and what it will not do. Your agent reads the one in play before it writes a line, through the AI Agent beside the page, or through eidos instructions in any terminal.
What you will use most
Claude Code or Codex beside the page, the open spec attached. /grill makes it ask before it writes, and your own slash commands share the prompts that work.
When the agent decides something on its own, it logs it as itself, and it waits unconfirmed until you stand behind it.
Tasks point at the spec they serve. The agent moves them, ticks their checklists, and writes what it learned as it goes.
eidos check reports a spec missing a section or a property, on your laptop and on every merge request.
Only you confirm
Every call lands in one table with its type, who logged it, and the specs it was made for. Anything the agent decided on its own arrives as Proposed, assigned to you, and shows in the spec as unconfirmed until you click Confirm.
No app required
The desktop app is optional. The same blueprints work from the CLI on npm, and one command points every agent that reads AGENTS.md at the workflow.
$ npm install -g eidosmd
$ eidos install @BuildableWorks/software
$ eidos agents --write
✓ created AGENTS.md with the Eidos nudge
$ eidos check
✓ no findingsStart here
Frames for the product, specs for the features, and a micro variant for the small ones. Pick it in the app when you make a new root, or install it from a terminal.
An app, a service, or a system
Frames for architecture, audience, criteria, and market, and specs grouped by domain.
$ eidos install @BuildableWorks/softwareIn the app: New Root, then pick it from the list.
Download Eidos MD, install the software framework, and write your first blueprint before the next session.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.