bp-init

Installs and updates the blueprint-harness engine, workspace, and AI skill copies in a target repository.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill bp-init-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bp-init
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/blueprint-harness/skills/bp-init
Command: npx skills add https://github.com/nico0695/ai-tools --skill bp-init-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up the blueprint-harness orchestration engine in a repository involves copying engine files, seeding configuration, wiring skills into AI assistant setups, and injecting wrapper blocks — a repetitive, error-prone process that this Skill automates with strict write boundaries and update detection. ## Core Features & Use Cases - Engine installation and updates: Copies the orchestrator, skills, schemas, and templates into .bp-harness/, comparing VERSION files to detect fresh installs, no-op repairs, or updates. - AI setup integration: Detects Claude Code (CLAUDE.md/.claude/) and AGENTS (AGENTS.md/.agents/) environments, copies bp-* skills into them, and injects marked wrapper blocks with user confirmation. - Workspace bootstrapping: Creates bp-workspace/ with objectives, ideas, bugs, and audits directories, seeds a schema-validated config.yaml, and detects capabilities like rg and gh. - Use Case: A developer clones a project and wants spec-driven development tooling; they run the installer once and get the engine, workspace, and AI assistant wrappers configured with at most two questions. ## Quick Start Ask the AI to run bp init to install blueprint-harness into the current repository.

Frequently Asked Questions about bp-init

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

FAQPage Schema
How do I install blueprint-harness into an existing repository?▼

Run the bp-init skill, which copies the engine into .bp-harness/, creates bp-workspace/ with a seeded config.yaml, and configures detected AI setups. It asks at most two questions and defaults the product name to the repository directory name.

How do I update blueprint-harness to a new version?▼

Re-run the installer; it compares .bp-harness/VERSION with the package VERSION and offers an update when they differ. Update mode re-copies the engine, refreshes skill copies and wrapper blocks, and leaves bp-workspace/ content untouched.

Does bp-init work with both Claude Code and AGENTS setups?▼

Yes, it detects CLAUDE.md/.claude/ for Claude Code and AGENTS.md/.agents/ for AGENTS. When multiple setups are detected it asks which to configure, then copies bp-* skills and injects wrapper blocks into each.

What files does the blueprint-harness installer never modify?▼

It never touches .gitignore, source code, or pre-existing bp-workspace/templates/ content, and it never creates objectives. Writes are limited to .bp-harness/, workspace config, skill copies, and confirmed wrapper or permission changes.

What happens if no AI setup is detected during installation?▼

The installer skips skill copying, wrapper injection, and the permission offer, installing only the engine and workspace. It reports this explicitly in the final summary.