Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub urso/claudev --plugin blueprintHow this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:design-updateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Update a design and its stories based on implementation learnings. Can update the design document, add new stories, adjust story dependencies, or cancel stories that are no longer needed.
Processes increment-request.json: orients on project state, elicits incremental EARS requirements with acceptance criteria, classifies changes, updates SRS/design docs, appends to feature-list.json.
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.
Update a design and its stories based on implementation learnings. Can update the design document, add new stories, adjust story dependencies, or cancel stories that are no longer needed.
${CLAUDE_PLUGIN_ROOT}/resources/discovery.md${CLAUDE_PLUGIN_ROOT}/resources/design-operations.md${CLAUDE_PLUGIN_ROOT}/resources/story-operations.md${CLAUDE_PLUGIN_ROOT}/scripts/query-stories.sh${CLAUDE_PLUGIN_ROOT}/scripts/set-status.sh${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh$ARGUMENTS
Parse for design file path, name, or ID.
!bash ${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh "" design
Read DISCOVERY_GUIDE, DESIGN_OPS, and STORY_OPS for available tools and procedures. Locate the design based on user input. Read the design document.
Use a sub-agent to read all stories and extract insights:
bash QUERY_STORIES --design <design-id>
Spawn a sub-agent with the story file paths and the design document:
Task: Extract design-relevant insights from stories
subagent_type: general-purpose
Read the design document at [design-file-path].
Read each of these story files: [story-file-paths]
Extract insights that may require updating the design:
- **Deviations**: Decisions in stories that changed the original design approach
- **New decisions**: Architecture decisions made during implementation not captured in the design
- **Blockers resolved**: Issues that required design-level changes
- **Open questions answered**: Questions from the design that stories resolved
- **Gaps**: Work discovered during implementation that isn't covered by any existing story
- **Obsolete stories**: Stories that are no longer needed due to approach changes
- **Dependency issues**: Stories whose blocked-by relationships need adjusting
Also report story statuses (how many done vs in-progress vs other).
Return a structured summary of findings. Only include items that are relevant — skip routine implementation details.
Read the workflow files listed in the pre-computed context above for design guidelines.
Present the sub-agent's findings to the user.
Ask user which updates to apply.
Update the design document with approved changes:
Follow the procedures in STORY_OPS for all story modifications. Based on the sub-agent's findings and user approval:
Only make changes the user explicitly approves.
Check story statuses from step 2:
If ALL stories for this design have status: done, suggest marking the design as done:
"All stories for this design are done. Mark design as done?"
If user agrees:
bash SET_STATUS design <id> done
Report what was updated (design changes, new stories, cancelled stories, dependency changes) and suggest next steps if applicable.