Plugin

blueprint-mode

Name: blueprint-mode
Author: rickardp

By rickardp

Spec-driven development with documented decision rationale: specs, ADRs, patterns, and requirements

Component Overview

Commands

ADR Agent, Combined Agent - All Document Types +5

Agents

blueprint:bad-pattern, blueprint:capture +10

Skills

PostToolUse, UserPromptSubmit

Hooks

MCP Servers

LSP Servers

Output Styles

Themes

Monitors

Install

npx claudepluginhub rickardp/blueprint-mode --plugin blueprint-mode

Component Details

Agents (7)

ADR Agent

/adr

You are the **ADR Agent**. Your ONLY responsibility is creating Architecture Decision Records that follow the exact format specified below.

Combined Agent - All Document Types

/all

You are creating a complete Blueprint structure. You must follow the EXACT formats for each document type. This reference covers ALL document types you may create.

Boundaries Agent

/boundaries

You are the **Boundaries Agent**. Your ONLY responsibility is creating agent boundary specifications that follow the exact format specified below.

Feature Spec Agent

/feature-spec

You are the **Feature Spec Agent**. Your ONLY responsibility is creating feature specifications that follow the exact format specified below.

Blueprint Mode - Agent Reference

/howto

This project uses Blueprint Mode for spec-driven development. Blueprint captures decision rationale (WHY), not detailed specs (WHAT). Read this before making changes.

NFR Agent

/nfr

You are the **NFR Agent** (Non-Functional Requirements). Your ONLY responsibility is creating NFR specifications that follow the exact format specified below.

Pattern Agent

/pattern

You are the **Pattern Agent**. Your responsibility is creating good patterns and documenting anti-patterns that follow the exact formats specified below.

Skills (12)

blueprint:bad-pattern

/bad-pattern

Document an anti-pattern to avoid

blueprint:capture

/capture

Capture decisions and context from the current conversation into blueprint docs

blueprint:decide

/decide

Record a technology decision as an ADR (triages mixed input into ADRs, feature specs, and NFRs)

blueprint:good-pattern

/good-pattern

Capture good code as a reusable example

blueprint:help

/help

Explain Blueprint Mode plugin and available commands. Use when the user asks about Blueprint features, how to use skills, or needs guidance on spec-driven development workflow.

blueprint:list-adrs

/list-adrs

List all Architecture Decision Records with their status and summaries. Use when the user wants to see all decisions, review ADR history, or find a specific decision.

blueprint:onboard

/onboard

Create Blueprint structure from existing repo. Run multiple times to refine.

blueprint:require

/require

Add a requirement (functional or non-functional)

blueprint:setup-repo

/setup-repo

Set up a new repository with spec-driven development structure from scratch. Use when creating a new project and the user wants to establish specs, ADRs, and patterns from the beginning.

blueprint:status

/status

Show overview of project's Blueprint structure including specs, ADRs, and patterns. Use when the user asks about documented decisions, project status, or wants to see what's been captured.

blueprint:supersede

/supersede

Replace or deprecate a previous architectural decision. Use when the user wants to change a tech choice, retire a decision, or remove functionality without replacement.

blueprint:validate

/validate

Check code against documented specs, patterns, anti-patterns, and ADR decisions. Use when the user wants to verify consistency, audit the codebase, check spec compliance, or find violations.

Hooks (1)

Review workflow modifications before installing

Event Hooks

File writes

2 hooks across 2 events

README

Blueprint Mode

Blueprint Mode is an attempt at creating a stable source of truth in the era of vibe coding and agentic AI assistants.

It attempts to solve the problem if maintainability in code repositories with large amounts of AI code while trying to stay out of the way. The following axioms are what Blueprint Mode is built on:

When code is the spec, AI rewrites your source of truth at will. We need a high level ground truth that is not changed on a whim. We want to keep humans in control of system design while letting AI deal with the details of the bulk of the code More time is spent maintaining a code base than writing the first version

The Problem

Code as the source of truth

This is what you typically get from vibe coding platforms like Lovable or Cursor (out of the box). Documentation is usually in the form of a README file and code comments.

Lost intent — you can't tell if code reflects a conscious decision or AI just picking something
Lost memory — AI forgets why you chose PostgreSQL over MongoDB last week
Lost consistency — different architectural choices each session
Lost boundaries — difficult to set up constraints and coding practices

Spec driven development and similar approaches

Traditional spec-driven development tries to solve the "code as truth" problem by creating detailed specifications before writing code. But this introduces its own set of problems:

Premature detail — you are forced to focus on details that is not yet on top of your mind
High friction — updating specs is tedious, so developers skip it or stop reading them entirely
Spec drift — specifications become outdated as code evolves, creating a second source of truth that contradicts the first
Wrong abstraction level — specs either become too detailed (duplicating code in English) or too vague (unhelpful)
No context for decisions — specs say what but rarely why - this is important to know when they are outdated

How It Works

Interview — Claude asks about your project, tech choices, and why you made them
Document — Decisions become ADRs, patterns get captured, boundaries get set
Develop — AI follows your documented decisions consistently
Evolve — Update decisions with /blueprint:decide or /blueprint:supersede

Quick Start

/plugin marketplace add rickardp/blueprint-mode
/plugin install blueprint-mode

Local development

To run a locally checked out version of the plugin (useful during development):

git clone https://github.com/rickardp/blueprint-mode.git
cd blueprint-mode
claude --plugin-dir ./plugins/blueprint-mode

The --plugin-dir flag loads the plugin directly from the specified directory, overriding any installed version with the same name. This allows you to test changes immediately without reinstalling.

You can also use an absolute path:

claude --plugin-dir /path/to/blueprint-mode/plugins/blueprint-mode

Commands

Command	Purpose
`/blueprint:setup-repo`	Set up new repository with spec structure
`/blueprint:onboard`	Add spec structure to existing codebase
`/blueprint:require`	Add functional or non-functional requirements
`/blueprint:decide`	Record technology/architecture decisions as ADRs
`/blueprint:good-pattern`	Capture approved code patterns
`/blueprint:bad-pattern`	Document anti-patterns to avoid
`/blueprint:supersede`	Replace previous decisions with new ones
`/blueprint:list-adrs`	List all ADRs with status and summaries
`/blueprint:status`	Show overview of project's Blueprint structure
`/blueprint:validate`	Check code against documented patterns and decisions
`/blueprint:help`	Explain Blueprint features and available commands

Onboarding an existing codebase

/blueprint:onboard

Also, the onboarding pushes the limits for what a skill can really do, so on more complex cases it may be worth running the onboarding multiple times (it will fill in gaps if it skipped over some files in the first run).

Setting up a new repo

/blueprint:setup-repo

Note that this functionality is in its early stages.

What Gets Created

View full README on GitHub

Similar Plugins

team-skills-platform

167.4k

1.5K

Team-oriented workflow plugin with role agents, 27 specialist agents, ECC-inspired commands, layered rules, and hooks skeleton.

Stats

Version1.2.0

Parent Repo Stars1

MaintenanceExcellent

LicenseMIT

AddedFeb 2, 2026

Actions

View on GitHub View README Plugin Marketplace JSON

Available In

blueprint-mode2 cascade-code-general-misc-2

Safety Signals

Caution

Modifies files

Hook triggers on file write and edit operations

Uses power tools

Uses Bash, Write, or Edit tools

Blueprint Mode

Blueprint Mode is an attempt at creating a stable source of truth in the era of vibe coding and agentic AI assistants.

It attempts to solve the problem if maintainability in code repositories with large amounts of AI code while trying to stay out of the way. The following axioms are what Blueprint Mode is built on:

When code is the spec, AI rewrites your source of truth at will. We need a high level ground truth that is not changed on a whim. We want to keep humans in control of system design while letting AI deal with the details of the bulk of the code More time is spent maintaining a code base than writing the first version

The Problem

Code as the source of truth

This is what you typically get from vibe coding platforms like Lovable or Cursor (out of the box). Documentation is usually in the form of a README file and code comments.

Lost intent — you can't tell if code reflects a conscious decision or AI just picking something
Lost memory — AI forgets why you chose PostgreSQL over MongoDB last week
Lost consistency — different architectural choices each session
Lost boundaries — difficult to set up constraints and coding practices

Spec driven development and similar approaches

Traditional spec-driven development tries to solve the "code as truth" problem by creating detailed specifications before writing code. But this introduces its own set of problems:

Premature detail — you are forced to focus on details that is not yet on top of your mind
High friction — updating specs is tedious, so developers skip it or stop reading them entirely
Spec drift — specifications become outdated as code evolves, creating a second source of truth that contradicts the first
Wrong abstraction level — specs either become too detailed (duplicating code in English) or too vague (unhelpful)
No context for decisions — specs say what but rarely why - this is important to know when they are outdated

How It Works

Interview — Claude asks about your project, tech choices, and why you made them
Document — Decisions become ADRs, patterns get captured, boundaries get set
Develop — AI follows your documented decisions consistently
Evolve — Update decisions with /blueprint:decide or /blueprint:supersede

Quick Start

/plugin marketplace add rickardp/blueprint-mode
/plugin install blueprint-mode

Local development

To run a locally checked out version of the plugin (useful during development):

git clone https://github.com/rickardp/blueprint-mode.git
cd blueprint-mode
claude --plugin-dir ./plugins/blueprint-mode

You can also use an absolute path:

claude --plugin-dir /path/to/blueprint-mode/plugins/blueprint-mode

Commands

Command	Purpose
`/blueprint:setup-repo`	Set up new repository with spec structure
`/blueprint:onboard`	Add spec structure to existing codebase
`/blueprint:require`	Add functional or non-functional requirements
`/blueprint:decide`	Record technology/architecture decisions as ADRs
`/blueprint:good-pattern`	Capture approved code patterns
`/blueprint:bad-pattern`	Document anti-patterns to avoid
`/blueprint:supersede`	Replace previous decisions with new ones
`/blueprint:list-adrs`	List all ADRs with status and summaries
`/blueprint:status`	Show overview of project's Blueprint structure
`/blueprint:validate`	Check code against documented patterns and decisions
`/blueprint:help`	Explain Blueprint features and available commands

Onboarding an existing codebase

/blueprint:onboard

Setting up a new repo

/blueprint:setup-repo

Note that this functionality is in its early stages.

blueprint-mode

Component Overview

Install

Component Details

Agents (7)

Skills (12)

Hooks (1)

README

Blueprint Mode

The Problem

Code as the source of truth

Spec driven development and similar approaches

How It Works

Quick Start

Commands

Onboarding an existing codebase

Setting up a new repo

What Gets Created

Similar Plugins

team-skills-platform

blueprint-mode

Component Overview

Install

Component Details

Agents (7)

Skills (12)

Hooks (1)

README

Blueprint Mode

The Problem

Code as the source of truth

Spec driven development and similar approaches

How It Works

Quick Start

Commands

Onboarding an existing codebase

Setting up a new repo

What Gets Created

Similar Plugins

team-skills-platform

claude-code-toolkit

fullstack-dev-skills

react-native-dev

prompts.chat

context7-plugin