Individual skill
blueprint-writing
How to write Blueprint-quality blueprints that AI agents can consume effectively. Covers implementation-agnostic blueprint design, testable acceptance criteria, hierarchical structure, cross-referencing, blueprint templates, greenfield and rewrite patterns, blueprint compaction, and gap analysis. Trigger phrases: "write blueprints", "create blueprints", "blueprint this out", "define requirements for agents", "how to write blueprints for AI"
plugins/JuliusBrussee/blueprint/skills/blueprint-writing/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 17,567 bytes
Read excerpt
# Blueprint Writing
## Core Principle: Blueprints Describe WHAT, Not HOW
Blueprints are **implementation-agnostic**. They define what the system must do and how to verify it, but never prescribe a specific framework, language, or architecture.
This is the fundamental distinction in Blueprint:
- **Blueprints** = WHAT must be true (framework-agnostic, durable, portable)
- **Plans** = HOW to build it (framework-specific, derived from blueprints)
- **Code** = the implementation (generated from plans, validated against blueprints)
### Why Implementation-Agnostic?
When blueprints avoid prescribing HOW, they become: