update

Update system blueprint sections affected by recent behavior changes.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/wrteam-jay/blueprint --skill update-wrteam-jay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/wrteam-jay/blueprint/tree/main/skills/blueprint/skills/update
Command: npx skills add https://github.com/wrteam-jay/blueprint --skill update-wrteam-jay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining up-to-date documentation for evolving systems, preventing documentation from becoming stale and inaccurate.

Core Features & Use Cases

  • Targeted Updates: Focuses on modifying only the sections of a blueprint affected by a specific system change.
  • Change Tracking: Integrates with changelogs and decision logs to record modifications.
  • Manifest Management: Updates the blueprint's README to reflect new versions and statuses.
  • Use Case: After deploying a new feature that introduces a new user role, use this Skill to update the actors.md and relevant scenarios/ files, ensuring the blueprint accurately reflects the current system.

Quick Start

Use the update skill to incrementally update the blueprint documentation to reflect a new system behavior.

Frequently Asked Questions about update

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

FAQPage Schema
How do I update system blueprints to reflect recent changes in behavior and flows?

To update system blueprints, identify affected files using a change-mapping table, read necessary sections, check for staleness, draft edits, and update changelogs and manifests to reflect recent changes in behavior and flows.

What is the best way to maintain documentation for evolving systems without rewriting everything?

Targeted updates focus on modifying only the blueprint sections affected by a specific system change, preventing documentation from becoming stale while avoiding the need to rewrite entire files.

How does change tracking work when updating blueprints for new system features?

Change tracking integrates with changelogs and decision logs to record modifications, while also updating the blueprint's README manifest to reflect new versions and statuses for new system features.

When should I use a targeted documentation update for system maintenance?

Use a targeted documentation update for system maintenance whenever you deploy changes that alter existing behavior, flows, rules, or terminology, ensuring blueprints accurately reflect the current system.

Do I need a change-mapping table to modify existing system blueprints?

Yes, a change-mapping table is required to identify affected files accurately, allowing the update process to read only necessary sections and check for staleness before drafting edits.

Why does documentation become stale after deploying new system rules or terminology?

Documentation becomes stale because system changes are not immediately reflected in existing files, requiring adherence to maintenance protocols to incrementally update blueprints with new rules or terminology.