Use after modifying existing systems to update blueprint documentation. Read blueprints with read_blueprint before changes, update with write_blueprint after. Prevents documentation drift.
Updates blueprint documentation after code changes to prevent documentation drift. Triggers after modifying existing systems to ensure docs match implementation.
/plugin marketplace add TheBushidoCollective/han/plugin install hashi-blueprints@hanThis skill is limited to using the following tools:
Documentation drifts from implementation when:
Read existing blueprint using MCP tools:
// Find the blueprint
const results = await search_blueprints({ keyword: "auth" });
// Read it to understand current documentation
const blueprint = await read_blueprint({ name: "authentication" });
Note what documentation exists:
Plan documentation updates alongside code changes
Re-read the blueprint to verify accuracy:
const current = await read_blueprint({ name: "authentication" });
Verify each section:
Update using MCP tool:
await write_blueprint({
name: "authentication",
summary: "Updated summary if needed",
content: updatedContent
});
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 hashi-blueprints hooks automatically:
Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.