claude

ecw

Enterprise change management workflow: risk classification, multi-domain collaborative analysis, requirements elicitation, adversarial spec review, implementation correctness verification, and business impact analysis

1 on GitHubby Aimeerrhythmv1.7.2MITupdated 5 months ago
/

Plugin ecw from marketplace enterprise-change-workflow in Aimeerrhythm/enterprise-change-workflow. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (15)

  • biz-impact-analysis

    Business impact assessment after code changes complete. Auto-runs after impl-verify for P0/P1; invoke manually via /ecw:biz-impact-analysis.

  • cross-review

    Cross-file consistency verification for document-heavy changes. Manual-only, invoke via /ecw:cross-review.

  • domain-collab

    Multi-domain requirement analysis. Use when a requirement spans 2+ business domains. Auto-routed by ecw:risk-classifier for cross-domain changes; invoke manually via /ecw:domain-collab.

  • impl-orchestration

    Use when executing implementation plans with independent tasks. Risk-aware subagent dispatch with per-task review.

  • impl-verify

    Implementation verification before marking a task done. Absorbs code-reviewer role in ECW workflow. Also invocable manually via /ecw:impl-verify.

  • knowledge-audit

    Knowledge base health audit. Scans knowledge docs, analyzes content composition, detects stale references, tiny/oversized files, three-criteria compliance, outputs health report and optimization suggestions.

  • knowledge-repomap

    Generate code structure index (Repo Map) from codebase. Use during ecw-init or after major refactors.

  • knowledge-track

    Knowledge doc utilization audit. Manual-only, invoke after a dev task to analyze how knowledge docs were used in the conversation.

  • requirements-elicitation

    Structured requirement elicitation before implementation. Auto-routed by ecw:risk-classifier for P0/P1 single-domain requirements; invoke manually via /ecw:requirements-elicitation.

  • risk-classifier

    Entry point for any new requirement, feature, or code change. Classifies risk (P0–P3) and routes to the appropriate workflow. Run before implementation; not for bug fixes (use ecw:systematic-debugging).

  • spec-challenge

    Adversarial review of design specs and solution documents. Auto-runs after ecw:writing-plans for P0 changes (any domain mode); invoke manually via /ecw:spec-challenge.

  • systematic-debugging

    Entry point for bug fixes. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Domain-knowledge-driven root cause analysis.

  • tdd

    Use when implementing any feature or bugfix, before writing implementation code. Risk-aware TDD with ecw.yml integration.

  • workspace

    Multi-repo workspace for cross-service development. Create isolated workspaces with git worktree, coordinate multi-session parallel implementation across independent services. Manual invocation only via /ecw:workspace.

  • writing-plans

    Use when you have a spec or requirements for a multi-step task, before touching code. Risk-aware planning with ECW domain context.

Slash commands (3)

  • /ecw:ecw-init

    Initialize Enterprise Change Workflow configuration for your project. Supports three modes — Attach (existing docs), Manual (user-specified paths), Scaffold (new project).

  • /ecw:ecw-upgrade

    Upgrade ECW configuration in your project. Runs idempotent checks and applies missing configuration items.

  • /ecw:ecw-validate-config

    Validate ECW configuration files for completeness and correctness. Checks for unfilled placeholders, missing files, and broken references.

Subagents (7)

  • biz-impact-analysis

    Analyzes business impact of code changes by combining structured dependency graph queries with incremental code scanning. Outputs a formatted impact report covering affected domains, downstream/upstream flows, external systems, and end-to-end paths. - Read - Grep - Glob - Bash

  • domain-analyst

    Domain-specific analysis agent for multi-domain collaboration. Dispatched by domain-collab Round 1 (independent analysis) and Round 2 (negotiation). Each instance focuses on a single domain's impact assessment. - Read - Grep - Glob

  • domain-negotiator

    Domain negotiation agent for multi-domain collaboration Round 2. Assesses whether other domains' change plans affect this domain. - Read - Grep - Glob

  • impl-verifier

    Implementation verification round agent for impl-verify. Each instance handles one verification dimension (requirements, domain rules, plan decisions, or engineering standards) independently. - Read - Grep - Glob - Bash

  • implementer

    Task implementer agent for impl-orchestration. Dispatched per plan task with full task context. Implements, tests, commits, and self-reviews. - Read - Edit - Write - Bash - Grep - Glob

  • spec-challenge

    Adversarial technical reviewer that challenges design specs and solution documents. Dispatched after a spec or design document is produced, reviews it from an independent context (only sees the document + project knowledge, not the author's reasoning). Outputs structured issues with severity and wor

  • spec-reviewer

    Spec compliance reviewer agent for impl-orchestration. Verifies implementer built what was requested — nothing more, nothing less. Reads actual code independently; does not trust implementer's report. - Read - Grep - Glob

View source on GitHub

Maintain ecw?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted