workflow-architect-issue-changer

Manage scope changes in workflow-architect with impact analysis and user approval.

65|8|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill workflow-architect-issue-changer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-architect-issue-changer
Source: https://github.com/EasyCode-Obsidian/workflow-architect/tree/main/claude/skills/workflow-architect-issue-changer
Command: npx skills add https://github.com/EasyCode-Obsidian/workflow-architect --skill workflow-architect-issue-changer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken scope changes by managing feature modifications and new requirements during a workflow-architect project, performing mandatory impact analysis before altering plans or execution state.

Core Features & Use Cases

  • Mid-Workflow Change Handling (Mode A): Pauses Phase 4 execution, analyzes impact, proposes an appropriate resolution path (light/moderate/major), then resumes without redoing unaffected completed work.
  • Post-Completion Change Handling (Mode B): Uses an abbreviated flow (abbreviated requirements → impact analysis → incremental planning/execution) to implement changes after completion.
  • Impact Analysis & Safety Gates: Scans workflow plan files and source code to classify severity and shows a user-confirmed impact summary before any modifications.

Quick Start

Use the workflow-architect issue changer to process a change request by saying: "/workflow-architect-issue-changer Add a notification system with email alerts and retries."

Frequently Asked Questions about workflow-architect-issue-changer

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

FAQPage Schema
How do I handle scope changes and new requirements during an active workflow execution?▼

The workflow-architect issue changer executes impact analysis on state.json and source files, classifies severity, and modifies plans after user approval, preventing broken scope changes mid-execution.

What is the best way to perform impact analysis before modifying a project plan?▼

Impact analysis scans .workflow/phases/ and source files to classify change severity, presenting a user-confirmed summary before modifying plans or code.

Can I add features to a completed workflow without redoing unaffected work?▼

Yes, post-completion incremental changes use an abbreviated flow to execute impact analysis and incremental planning, delivering new features without redoing unaffected completed work.

How do I safely pause execution to process a change request in state management?▼

To safely process a change request, pause Phase 4 execution, read state.json, record the change request, and propose a severity-based resolution path before resuming workflow execution.

Does this change management approach support incremental delivery for moderate severity modifications?▼

Yes, the approach supports incremental delivery by proposing severity-based resolution paths—light, moderate, or major—and executing targeted incremental planning for modifications.

Why do I need to scan source files when managing plan modification requests?▼

Scanning source files is required to accurately classify modification severity, ensuring impact analysis captures all affected plans and files before altering execution state.