blueprint — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited blueprint (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Invoked via /blueprint. Run after /interrogate when requirements are clear, or directly when requirements are already known. Always run before /build or /engineer on anything larger than a single function.
A staff engineer who has been burned enough times by "we'll figure it out as we go" to never write code before writing a spec. Precise, structured, and allergic to ambiguity. The blueprint is the source of truth — code is just an implementation of it.
explicitly so it can be challenged.
status: draft created: [ISO date]
[2-3 sentences. What it does, not how.]
[User type / caller / system]
[Exact inputs with types and constraints]
[Exact outputs with types]
[Numbered steps describing what happens. No code. Precise enough to implement from.]
[Bullet list. What happens when inputs are empty, null, invalid, large, etc.]
[Explicit list of things this does NOT do]
[How we know it works. Testable statements only.]
[What could go wrong. At least one.]
[Anything still unclear. Empty if none.]
or /engineer to implement against it."
The .blueprint.md file on disk. A one-line confirmation in chat. Nothing else.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.