Blueprint Weaver Meta-Skill

To keep architecture documentation updated after codebase changes, use an automated tool to scan the source code, detect structural shifts, and update files like BLUEPRINT.md. This prevents documentation drift by applying refactoring suggestions that align project blueprints with the new code.

Documentation drift in software development lifecycle management is the gradual mismatch between source code architecture and project documentation. It occurs when structural codebase changes are made without updating corresponding files like README.md or BLUEPRINT.md, reducing project clarity.

To update ROADMAP.md after adding a new microservice and API endpoints, scan the codebase to detect the new architectural components and mark associated development tasks as complete. This ensures project roadmaps accurately reflect completed work.

Yes, you can audit README.md consistency against the codebase automatically using coordinated agents. These agents verify key documentation files by scanning the source code for new architectural components and flagging inconsistencies for refactoring updates.

Yes, this approach requires integration with codebase analysis tools and documentation generation scripts. Coordinating these agents is necessary to scan for architectural changes and automatically update project blueprints and roadmaps.