Skip to content

LiorCohen/sdd / plugin/core/skills/orchestrators/change-orchestration

change-orchestration

Verified

Orchestrates the full change lifecycle — routes actions to phase-specific sub-files.

FileKindSize
SKILL.mdskill md4.2 KB
creation.mdmarkdown7.4 KB
implementation.mdmarkdown2.2 KB
management.mdmarkdown7.0 KB
planning.mdmarkdown1.9 KB
spec-review.mdmarkdown2.7 KB
verification.mdmarkdown4.3 KB

management.md

View on GitHub
# Management Actions

Handles `status`, `list`, `continue`, `regress`, and `request-changes` actions for the change orchestration skill.

---

## Action: status

Show current workflow state and all change IDs.

### Usage

```
/sdd-run change status [<change-id>]
```

### Flow

1. Read all workflows from `sdd/workflows/`
2. If `<change-id>` provided, show details for that specific change
3. Otherwise, for each workflow, display:
   - Workflow ID and source
   - Current item being worked on
   - All items with their statuses and change IDs

### Output

```
===============================================================
 WORKFLOW STATUS
===============================================================

Workflow: a1b2c3 (user-auth)
Source: external
Created: 2026-02-05

Current: [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/) (Registration) - spec_review

ITEMS:
  user-auth-1  Registration         spec_review    [changes/...](changes/2026/02/05/a1b2c3-user-auth/01-registration/)
  user-auth-2  Authentication       pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/...)
  user-auth-3  Password Reset       pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/...)
  user-auth-4  Analytics            pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/...)
  user-auth-5  Settings             pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/...)

NEXT ACTION:
  Review spec at: [SPEC.md](changes/2026/02/05/a1b2c3-user-auth/01-registration/SPEC.md)
  Then: /sdd I want to approve the spec
```

---

## Action: list

List all changes in the specified workflow (or all workflows if multiple exist).

### Usage

```
/sdd-run change list
```

### Flow

1. Read workflow state for specified workflow (or all active workflows)
2. Display all items with details, grouped by workflow if multiple exist

### Output

```
===============================================================
 CHANGES IN WORKFLOW a1b2c3 (user-auth)
===============================================================

ID        TITLE                 TYPE      STATUS         LOCATION
───────── ───────────────────── ───────── ────────────── ─────────────────────────
user-auth-1    Registration          feature   spec_review    [changes/...](changes/2026/02/05/a1b2c3-user-auth/01-registration/)
user-auth-2    Authentication        feature   pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/02-authentication/)
user-auth-3    Password Reset        feature   pending        [sdd/workflows/...](sdd/workflows/a1b2c3-user-auth/drafts/03-password-reset/)

Dependencies:
  [user-auth-2](changes/2026/02/05/a1b2c3-user-auth/02-authentication/) depends on: [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/)
  [user-auth-3](changes/2026/02/05/a1b2c3-user-auth/03-password-reset/) depends on: [user-auth-2](changes/2026/02/05/a1b2c3-user-auth/02-authentication/)
```

---

## Action: continue

Resume current workflow from persisted state.

### Usage

```
/sdd-run change continue <change-id>
```

### Flow

1. Read workflow state from `sdd/workflows/`
2. Find current item (or specified change-id)
3. Based on status, take appropriate action:

| Status | Action |
|--------|--------|
| `pending` | Start spec solicitation |
| `soliciting` | Resume spec solicitation from saved state |
| `spec_review` | Prompt to review spec, suggest approve command |
| `plan_review` | Prompt to review plan, suggest approve command |
| `plan_approved` | Prompt to start implementation |
| `implementing` | Resume implementation from saved state |
| `verifying` | Continue verification |

### Output (example: soliciting)

```
Resuming workflow a1b2c3 (user-auth)...

Current: [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/) (Registration)
Status: soliciting (spec creation in progress)

Previously collected:
  - Problem: User registration flow
  - Primary user: New users
  - Requirements: 3 collected

Continuing from: Step 5 - Acceptance Criteria

For the requirement "Users can register with email":
What acceptance criteria should we have?
```

---

## Action: regress

🟡 **Caution:** This action resets workflow progress. The current plan or implementation is archived, but all progress beyond the target phase is reset. Dependent items are flagged for re-review. **Warn the user and confirm before executing.**

Go back to an earlier phase (e.g., from planning back to spec).

### Usage

```
/sdd-run change regress <change-id> --to <phase> --reason "<reason>"
```

### Arguments

| Argument | Required | Description |
|----------|----------|-------------|
| `change-id` | Yes | The change to regress |
| `--to` | Yes | Target phase: `spec` or `plan` |
| `--reason` | Yes | Reason for regression |

### Flow

1. Validate change exists
2. Archive current state via system CLI:
   ```bash
   <plugin-root>/system/system-run.sh archive store --source <prepared-dir> --type workflow-regression --json
   ```
3. Reset status fields for target phase and later
4. Flag dependent items for re-review
5. Log regression reason

### Output

```
Regressing [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/) to spec phase...

Reason: Need to add additional auth method

Archived:
  [PLAN.md](sdd/archive/workflow-regressions/20260205-1200-user-auth-1-impl/PLAN.md) → [sdd/archive/...](sdd/archive/workflow-regressions/20260205-1200-user-auth-1-impl/PLAN.md)

Status changes:
  spec_status: approved → needs_rereview
  plan_status: approved → pending

Dependent items flagged for re-review:
  [user-auth-2](changes/2026/02/05/a1b2c3-user-auth/02-authentication/) (Authentication) - depends on user-auth-1

NEXT STEPS:
  Edit [SPEC.md](changes/2026/02/05/a1b2c3-user-auth/01-registration/SPEC.md) to add auth requirements
  Then: /sdd I want to approve the spec
```

---

## Action: request-changes

🟡 **Caution:** This action resets implementation status from `complete` to `in_progress`, requiring the developer to rework. **Warn the user and confirm before executing.**

Request changes during the review phase.

### Usage

```
/sdd-run change request-changes <change-id> --reason "<reason>"
```

### Arguments

| Argument | Required | Description |
|----------|----------|-------------|
| `change-id` | Yes | The change to request changes for |
| `--reason` | Yes | What changes are needed |

### Flow

1. Validate change exists and `review_status: ready_for_review`
2. Update `review_status: changes_requested`
3. Log the reason in workflow state
4. Reset `impl_status` to allow re-implementation

### Output

```
Requesting changes for: [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/) (Registration)

Reason: Error messages need to be more user-friendly

Status changes:
  review_status: ready_for_review → changes_requested
  impl_status: complete → in_progress

NEXT STEPS:
  Address the feedback
  Then: /sdd I want to submit for review
```
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall