Manage requirement changes with impact analysis and change history.
npx skills add https://github.com/arch-team/devpace --skill pace-change
Please help me install this Agent Skill. Skill: pace-change Source: https://github.com/arch-team/devpace/tree/main/skills/pace-change Command: npx skills add https://github.com/arch-team/devpace --skill pace-change
This Skill streamlines the process of managing changes to project requirements, ensuring that additions, pauses, resumptions, reprioritizations, and modifications are handled in an orderly and traceable manner.
/pace-change add to insert it, analyze its impact on the current plan, and confirm the adjustment.Use the pace-change skill to add a new requirement for user authentication.
High-intent search queries and answers about installing and using this skill.
Requirement changes are managed by adding, pausing, resuming, reprioritizing, or modifying requirements. The skill performs automated impact analysis and risk assessment to ensure mid-sprint adjustments remain orderly and traceable.
Impact analysis for new feature requests is performed automatically during the requirement modification process. It assesses potential risks and impacts on the current project plan, providing goal-to-code traceability before you confirm the adjustment.
Yes, batch operations allow multiple requirement changes to be processed together. This functionality supports adding, pausing, and reprioritizing several requirements simultaneously while maintaining a complete change history log.
Goal-to-code traceability is maintained through guided user interaction and a comprehensive change history log. Reprioritizing requirements triggers impact analysis, ensuring every modification is tracked and aligned with project goals.
Change history tracking logs all requirement modifications, including pauses and resumptions. This provides a complete audit trail of when and how requirements were adjusted, ensuring full traceability throughout the project lifecycle.
Yes, pace-change supports agile change control by handling mid-sprint requirement adjustments. It inserts new stakeholder requests, analyzes their impact on the current plan, and confirms the adjustment through guided user interaction.
Eigo-Mt-FujiAnalyze change impact and validate delta specifications for brownfield systems.
MattVOLTARank cross-project Todoist task risks using email, log, and calendar signals.
hmzainjamilAutomate Jira issue management, sprint planning, and workflow transitions.
Yi-ming-ZhaoBatch-archive completed OpenSpec changes with metadata and per-change reports.