blueprint-docs

Refresh and verify Blueprint repository docs against saved evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically refresh and verify Blueprint repository documentation to keep docs aligned with the codebase and preserve a durable, auditable docs-update record.

Core Features & Use Cases

  • Automated documentation refresh: refresh selected repo docs from saved evidence to maintain accuracy.
  • Verification with evidence: compare repo docs against saved Blueprint evidence to detect drift.
  • Durable reporting: persist a scoped docs-update report that can be reviewed and versioned without broad repo mutations.

Quick Start

Run /blu-docs-update to refresh and verify repository docs using saved evidence.

Frequently Asked Questions about blueprint-docs

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

FAQPage Schema
How do I automatically refresh repository documentation to match codebase changes?

Automated documentation refresh aligns selected repo docs with saved evidence to maintain accuracy. Running /blu-docs-update triggers the refresh cycle, verifying Blueprint repository docs against stored evidence and persisting a scoped docs-update report.

How does documentation verification against saved evidence work?

Documentation verification compares repo docs against saved Blueprint evidence to detect drift. It uses repo truth for evidence, invokes ecosystem tools through FQNs, and generates a durable report confirming whether selected docs remain accurately aligned.

What's the best way to keep Blueprint documentation aligned without broad repository mutations?

Keeping Blueprint documentation aligned without broad mutations requires scoping changes narrowly to selected docs. The refresh process verifies against saved evidence and persists a durable, auditable docs-update report in the dedicated blueprint artifacts channel.

Do I need saved evidence to run a documentation update for Blueprint repositories?

Saved evidence is required to run a documentation update for Blueprint repositories. The update process relies on repo truth for evidence to verify alignment, detect drift, and generate a scoped docs-update report in the blueprint artifacts channel.

When should I avoid using automated docs refresh for repository documentation?

Avoid automated docs refresh when broad repository mutations are necessary or when saved evidence is unavailable. The process keeps changes narrowly scoped to selected docs, so extensive updates across unrelated files require alternative documentation management approaches.