Skip to content

v0.1.0 — first release

Choose a tag to compare

View all tags
@Potato7711 Potato7711 released this 25 Aug 20:11
· 5 commits to main since this release
v0.1.0
33fa92a

Blueprint is a folder of instructions you copy into a project. It gives an AI coding agent a lifecycle it cannot skip, rules that outrank the prompt, a memory that survives between sessions, and a definition of done that requires evidence.

It is not an agent or a model. It is the layer that makes the agent you already use behave like a professional engineer.

What is in this release

  • Constitution — eleven non-negotiable rules, anchored on evidence over claims.
  • Workflow — DISCOVER → DESIGN → PLAN → BUILD → VERIFY → SHIP, with an explicit gate rule: you cannot enter a phase until the previous one's exit criteria are recorded.
  • State — one state.md holding phase, current task, completed work with evidence, blockers, decisions and the next action. A cold session reads it and continues.
  • Loops — per task: IMPLEMENT → TEST → REVIEW → FIX → VERIFY, with a two-attempt limit and a structured blocker format.
  • blueprint/validate.py — standard-library-only check for state structure, phase gates, evidence lines and ADR consistency, plus a --release scan for secrets and personal data.
  • Adapters — AGENTS.md and CLAUDE.md, pointers only. Claude Code, Codex, Cursor and Gemini CLI, with no per-vendor copy of the method to drift apart.
  • Example — a complete run in examples/task-tracker, from a vague idea to a working, tested tool.

Install

git clone --depth 1 https://github.com/Potato7711/blueprint.git /tmp/blueprint
cp -r /tmp/blueprint/blueprint /tmp/blueprint/AGENTS.md your-project/

Then tell your agent: Read blueprint/START-HERE.md and follow it.

The bug that made the case

Dogfooding found three real defects before release. The example crashed with UnicodeEncodeError on its ordinary list --all path: the design specified a tick character, and the unit tests captured stdout with io.StringIO, which never encodes — so a crash survived a fully green suite until the tool was run in a real terminal during VERIFY.

The same class of bug turned up in its error messages, and again in Blueprint's own validator output. All three are fixed, and capturing output is not the same as writing it is now a documented VERIFY failure mode.

Requirements: Python 3.9+ for the optional validator. Nothing else.

Assets 2
Loading