blueprint-capture

Capture ideas, notes, and backlog entries into the local .blueprint workspace.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rakole/blueprint --skill blueprint-capture-rakole
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint-capture
Source: https://github.com/rakole/blueprint/tree/main/skills/blueprint-capture
Command: npx skills add https://github.com/rakole/blueprint --skill blueprint-capture-rakole

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and organize ideas, notes, and backlog entries locally within the repository, ensuring ideas persist alongside code and are not lost in chat history or external tools.

Core Features & Use Cases

  • Deterministic notes and backlog capture stored under .blueprint/
  • Enforces MCP-owned persistence and communicates unimplemented capture commands clearly
  • Supports common capture commands: note, add-todo, check-todos, add-backlog, review-backlog, explore

Quick Start

Record a new idea as a note inside the local .blueprint directory and tag it for later processing.

Frequently Asked Questions about blueprint-capture

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

FAQPage Schema
How do I capture backlog ideas and notes directly inside my repository?

You can capture backlog ideas by writing notes directly into the local .blueprint workspace directory. This ensures ideas persist durably in-repo alongside your code instead of getting lost in chat history.

What is the best way to keep project backlog entries synchronized with MCP tools?

Keeping project backlog entries aligned with MCP tools requires enforcing MCP-owned persistence contracts. This approach uses deterministic capture commands to guarantee durable writes that integrate seamlessly across team sessions.

Can I scope tasks and hand off backlog items to other team members locally?

Yes, you can scope tasks and hand off backlog items locally using defined capture contracts. By operating within the .blueprint workspace, entries remain accessible across different sessions and team members.

How do I use /blu-* commands to add and review backlog entries?

You use /blu-* commands like add-backlog, review-backlog, and add-todo to input and manage entries. These commands trigger deterministic capture contracts that write data directly to the local .blueprint directory.

Does in-repo idea capture work without external note-taking tools?

Yes, in-repo idea capture works without external note-taking tools by storing everything locally. It uses the .blueprint directory to enforce durable writes, ensuring your notes and todos remain version-controlled.

Why should I store project notes in the .blueprint directory instead of chat history?

Storing project notes in the .blueprint directory prevents ideas from being lost in ephemeral chat history. It provides deterministic, durable writes that maintain context and backlog entries directly alongside your code.