Help us improve
Share bugs, ideas, or general feedback.
From blueprints
Maintains blueprint documentation after system modifications to prevent drift. Guides finding, reading, verifying, and updating blueprints using Grep, Read, Write tools.
npx claudepluginhub thebushidocollective/han --plugin blueprintsHow this skill is triggered — by the user, by Claude, or both
Slash command
/blueprints:blueprints-maintenanceThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Documentation drifts from implementation when:
Creates or updates technical blueprint documentation for features, APIs, and architecture. Searches existing blueprints first via Glob/Grep to avoid duplication, using standard structure and frontmatter.
Displays blueprint status: version, config, doc counts (PRDs/ADRs/PRPs), task schedules, upgrade availability, and generated rules integrity.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Documentation drifts from implementation when:
Find relevant blueprints:
# Search for blueprints related to your system
Grep("auth", path: "blueprints/", output_mode: "files_with_matches")
# Read the blueprint to understand current documentation
Read("blueprints/authentication.md")
Note what documentation exists:
Plan documentation updates alongside code changes
Re-read the blueprint to verify accuracy:
Read("blueprints/authentication.md")
Verify each section:
Update the blueprint:
# Read current content, modify as needed, write back
Write("blueprints/authentication.md", updated_content_with_frontmatter)
Remove stale content - outdated docs mislead
When adding functionality:
When changing behavior:
When deprecating or removing:
When restructuring without behavior changes:
Signs blueprints need attention:
Prioritize by impact:
When reviewing blueprints:
## Verification Checklist
- [ ] Overview matches current purpose
- [ ] All public APIs documented
- [ ] API signatures accurate
- [ ] Examples execute correctly
- [ ] Behavior matches implementation
- [ ] File paths exist
- [ ] No removed features documented
- [ ] Related systems links work
- [ ] No duplicate content with other blueprints
/blueprints command to regenerateThe blueprints hooks automatically: