blueprints-maintenance

Blueprint drift occurs when documentation lags behind code modifications. Use read_blueprint to audit current coverage, then write_blueprint to publish updates across Overview, API docs, behavior notes, and file paths after making changes, ensuring documentation reflects your current system state.

Update Overview sections describing system purpose, API documentation with current signatures and examples, behavior notes capturing how components interact, and file paths reflecting the actual codebase structure. Validate each section for accuracy and consistency before publishing.

Yes. This Skill reads existing blueprints via MCP tooling, compares them against code changes, plans documentation updates, and writes revised blueprints atomically. This prevents manual drift and keeps documentation aligned with each modification cycle.

Outdated blueprints mislead developers, slow onboarding, and create maintenance friction. Regular blueprint verification and updates using read_blueprint and write_blueprint ensure your documentation stays a reliable source of truth as systems evolve.

The Skill verifies API signatures match code, examples run correctly against current interfaces, file paths point to actual locations, and behavior descriptions reflect real system logic. Atomic updates ensure all sections remain consistent across Overview, APIs, notes, and paths.

Strategic updates during maintenance cycles reduce drift accumulation. Use read_blueprint to identify gaps and write_blueprint for batch updates rather than single-change documentation, balancing coverage with development velocity.