From prism-devtools
Use when handling sprint changes or scope adjustments. Analyzes change impacts, re-estimates affected stories, and adjusts sprint capacity using PRISM principles.
npx claudepluginhub resolve-io/.prismThis skill uses the workspace's default tool permissions.
<!-- Powered by PRISMâ„¢ Core -->
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
Guide a structured response to change triggers using PRISM principles and PSP/TSP measurement:
Acknowledge Change & Measure Impact:
PSP/TSP Metrics to Consider:
Predictability Impact:
Resilience Considerations:
Intentionality Check:
Sustainability Analysis:
Maintainability Review:
For each affected story:
re_estimation:
original_estimate:
story_points: X
size_category: Y
hours: Z
change_impact:
scope_change: "+/-N%"
complexity_change: "increased|decreased|same"
risk_change: "higher|lower|same"
new_estimate:
story_points: X'
size_category: Y'
hours: Z'
confidence: "high|medium|low"
justification: "Clear explanation of estimate change"
sprint_metrics:
original:
total_points: X
total_hours: Y
team_capacity: Z
after_change:
total_points: X'
total_hours: Y'
team_capacity: Z'
options:
- absorb: "Take the hit, extend hours"
- defer: "Move stories to next sprint"
- swap: "Replace with smaller stories"
- descope: "Reduce story scope"
Create proposal document with:
Executive Summary:
Metrics Impact:
Story-Level Changes: For each affected story:
Team Considerations:
Proposed Actions:
Record in estimation-history.yaml:
change_events:
- date: YYYY-MM-DD
sprint: N
trigger: "requirement change|bug|scope creep"
stories_affected: [X.Y, X.Z]
estimation_impact:
total_points_change: +/-N
accuracy_impact: "X%"
lessons_learned: |
- Specific insight about estimation
- Pattern identified for future
improvement_actions:
- "Add buffer for similar changes"
- "Update estimation proxies"
Sprint Adjustment Meeting Agenda:
Key Messages:
Primary: Sprint Change Proposal (markdown)
Secondary: Updated Artifacts