Route frozen document changes through Scrum approval and update revision history.
npx skills add https://github.com/sohei56/maul-team --skill change-process
Please help me install this Agent Skill. Skill: change-process Source: https://github.com/sohei56/maul-team/tree/main/skills/change-process Command: npx skills add https://github.com/sohei56/maul-team --skill change-process
This Skill provides a controlled process for modifying frozen product documents while preserving approval records, scope traceability, and developer alignment.
Ask the change-process skill to evaluate and process a proposed change to a frozen document, including its path, rationale, details, affected PBI IDs, and approval decision.
High-intent search queries and answers about installing and using this skill.
To manage approved changes to frozen product documents in Scrum, route modification requests through Scrum Master and Product Owner approval workflows, update revision history metadata, and reflect approved scope changes in backlog.json to notify Developers.
The approval workflow for updating sprint scope or product briefs requires explicit approval or rejection from the Product Owner, logs PO decisions in agent mode, updates revision history with affected PBIs, and syncs backlog.json to notify Developers of approved changes.
Track revision history for product backlog item changes by preserving revision_history metadata that records the sprint, author, date, affected PBI IDs, change summary, and a change-process marker to maintain scope traceability and an auditable decision trail.
Yes, you can use an agent to act as the Product Owner for change requests; the agent-based PO workflow supports recording PO decisions, evaluating proposed changes to frozen documents, and updating the backlog to notify Developers of approved modifications.
To process a proposed change to a frozen vision document, provide the document path, rationale, details, and affected PBI IDs to the change-process skill, which evaluates the request, routes it for approval, updates revision history, and syncs backlog.json.
Modifying frozen documents without approval bypasses scope control, breaks revision history traceability, leaves backlog.json out of sync, and prevents Developers from receiving notifications regarding approved scope changes affecting product backlog items.
polseguCompare current implementation and active work against original scope plans.
RDEWAIValidate and update sprint backlogs to Approved status with metadata changes.
lukeiversGenerate structured summaries with decisions, rationales, and recommendations.
sohei56Refine draft Scrum backlog items into implementation-ready PBIs with acceptance criteria.
