blueprint-guard

Check shaped issues against project blueprints and record fit in 00_brainstorm.md.

1|1|Updated Apr 18, 2026

Search Tags:#architecture #verification #compliance #blueprint #guard #branch-policy #release-policy

Ready to run

npx skills add https://github.com/emmepra/ora-et-labora --skill blueprint-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blueprint-guard
Source: https://github.com/emmepra/ora-et-labora/tree/main/skills/blueprint-guard
Command: npx skills add https://github.com/emmepra/ora-et-labora --skill blueprint-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

blueprint guard prevents implementation from drifting away from the durable project model. It checks whether the shaped issue fits the repo's architecture, contracts, runtime assumptions, verification policy, branch model, and release policy.

Core Features & Use Cases

Identify the relevant blueprint files in the target repo or worktree.
Evaluate fit against surfaces such as architecture, API contracts, schema contracts, runtime and CI rules, and release/branch policies.
Record the fit result in 00_brainstorm.md and stop implementation when conflicts exist or when a durable blueprint update is required.
Keep durable project knowledge separate from task-local history.

Quick Start

Run blueprint guard on the shaped issue to verify alignment with the project blueprint and record the result in 00_brainstorm.md.

Frequently Asked Questions about blueprint-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify an issue fits my project architecture before starting implementation?▼

Blueprint fit checks verify that shaped issues align with the project's durable model, including architecture, contracts, runtime rules, and release policies, stopping progress when conflicts are detected.

What is blueprint compliance verification and when do I need it?▼

Blueprint compliance verification ensures implementation does not drift from the durable project model. You need it when an issue may conflict with architecture, API contracts, schema contracts, or branch policies.

How do I check branch and release policies against a new development task?▼

Checking branch and release policies involves evaluating the shaped issue against the repo's release and branch policies, recording findings in 00_brainstorm.md, and stopping if mandatory blueprint updates are required.

Does blueprint guard work with existing CI rules and runtime assumptions?▼

Blueprint guard evaluates fit against runtime and CI rules in the target repo or worktree, identifying relevant blueprint surfaces and assessing whether the shaped issue aligns with these constraints.

What happens when a blueprint fit check detects a conflict with the project architecture?▼

When a conflict is detected, findings are recorded in 00_brainstorm.md and implementation is stopped to prevent drift from the durable blueprint until the conflict is resolved or a mandatory update is completed.

Why should I keep durable project knowledge separate from task-local history?▼

Keeping durable project knowledge separate from task-local history preserves the integrity of the blueprint model so that future fit checks accurately reflect the repo's architecture, contracts, and policies.