LiorCohen/sdd / plugin/core/skills/orchestrators/change-orchestration
change-orchestration
VerifiedOrchestrates the full change lifecycle — routes actions to phase-specific sub-files.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.2 KB |
| creation.md | markdown | 7.4 KB |
| implementation.md | markdown | 2.2 KB |
| management.md | markdown | 7.0 KB |
| planning.md | markdown | 1.9 KB |
| spec-review.md | markdown | 2.7 KB |
| verification.md | markdown | 4.3 KB |
implementation.md
View on GitHub# Implementation Action
Handles the `implement` action for the change orchestration skill.
## Usage
```
/sdd-run change implement <change-id>
```
## Flow
### Step 1: Validate Status
1. Check status is `plan_approved`
2. If not, display error with current status
### Step 2: Load Spec and Plan (REQUIRED)
**CRITICAL**: Before ANY implementation:
- Read the ENTIRE PLAN.md
- Read the ENTIRE SPEC.md
- Understand ALL requirements
- Display comprehensive summary
### Step 3: Execute Domain Updates
From SPEC.md `## Domain Updates` section:
1. Add/update glossary terms
2. Create/update definition specs
3. Apply architecture updates
### Step 4: Execute Implementation Phases
For each phase in PLAN.md:
1. Read phase details
2. Determine the agent for this phase's component type:
- Read `components.<type>.agent` from tech pack manifest via `techpacks.readManifest`
- Load the agent via `techpacks.loadAgent(agent_name)`
3. Invoke the loaded agent with `techpacks.routeSkills(phase: implementation, component_type: <type>)` for standards
4. Verify deliverables
5. Update PLAN.md state
6. Create checkpoint commit
### Step 5: Track Progress
Update PLAN.md after each phase:
- Current Phase
- Completed Phases
- Actual Files Changed
- Blockers (if any)
This enables session resumption.
### Step 6: Update Status
When all phases complete:
```yaml
INVOKE workflow-state.update_status with:
change_id: <change_id>
status: verifying
```
## Output
```
Implementing: [user-auth-1](changes/2026/02/05/a1b2c3-user-auth/01-registration/) (Registration)
Step 1: Loading spec and plan...
Read [PLAN.md](changes/2026/02/05/a1b2c3-user-auth/01-registration/PLAN.md)
Read [SPEC.md](changes/2026/02/05/a1b2c3-user-auth/01-registration/SPEC.md)
[Displays comprehensive summary]
Step 2: Executing Domain Updates...
Adding glossary term: User
Creating definition: [specs/domain/definitions/user.md](specs/domain/definitions/user.md)
Domain updates complete
Step 3: Beginning implementation phases...
Phase 1: API Contract
Agent: <loaded via techpacks.loadAgent from manifest>
[Implementation progress...]
Phase 1 complete
[... continues through all phases ...]
Implementation complete. Ready for verification.
/sdd I want to verify the implementation
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |