Rickardp Blueprint Mode
rickardp-blueprint-mode is a Claude Code plugin for the Validate phase that structures spec-driven development with documented requirements, decisions, and rationale for AI-assisted coding.
by rickardp · github.com/rickardp/blueprint-mode
Run spec-driven development in Claude Code so requirements and design decisions stay documented while you build.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install rickardp-blueprint-mode@rickardp/blueprint-modeBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:rickardp/blueprint-mode") and the paste-ready config with skillselion.get_install_config("plugin:rickardp/blueprint-mode").
What it does
rickardp-blueprint-mode is a one-plugin Claude Code bundle for solo builders who want spec-driven development when pairing with an AI coder. Instead of jumping straight to files and diffs, you steer Claude through documented requirements, explicit decisions, and rationale so the agent has an authoritative blueprint to implement against. That matters for indies who lose context across sessions: the spec becomes the contract you can re-invoke after interruptions or model switches. The mode emphasizes patterns and documented intent rather than one-off chat improvisation, which pairs well with validate-then-build habits—scope the feature, record tradeoffs, then let implementation trace back to the same artifact. It is not a marketplace of unrelated skills; it is a focused discipline plugin for builders who already use Claude Code and want less thrash between “what we agreed” and “what shipped.” Complexity sits at intermediate because you need comfort writing concise specs and enforcing them during agent turns.
Highlights
- Spec-driven workflow tuned for AI-assisted coding with blueprint-style structure
- Captures decisions and rationale alongside requirements for later audits
- Patterns and documented modes reduce rework when the agent drifts from intent
- Single-plugin bundle focused on blueprint/spec discipline—not a general skill pack
- Keywords surface spec-driven, requirements, and decision logging for catalog search
Why builders use it
Solo builders using Claude often ship code that no longer matches what they briefly described in chat, with no durable spec or decision log to recover from.
You get a repeatable blueprint-style spec workflow so implementation stays tied to written requirements and recorded rationale across agent sessions.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is rickardp-blueprint-mode for?
It is for solo and indie builders using Claude Code who want spec-driven development with documented requirements and decisions instead of prompt-only coding.
When should I use rickardp-blueprint-mode?
Use it when you are scoping a feature or refactor and need a written blueprint before the agent implements, or when you want to audit drift against an earlier spec.
How do I add rickardp-blueprint-mode to my agent?
Install the plugin from the rickardp/blueprint-mode repository into Claude Code, enable the bundle, and invoke blueprint/spec mode when starting scoped work.
Comments
Share how you use rickardp-blueprint-mode, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.