# cc:gen:impl-change

> Implementation workflow

- Author: chrischeng-c4
- Repository: chrischeng-c4/cclab
- Version: 20260126151830
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/chrischeng-c4/cclab
- Web: https://mule.run/skillshub/@@chrischeng-c4/cclab~cc:gen:impl-change:20260126151830

---

---
name: cc:gen:impl-change
description: Implementation workflow
user-invocable: true
---

# /cc:gen:impl-change

Orchestrates the implementation phase, handling code generation, review, and iterative fixes based on the current state.

## IMPORTANT: Your role is orchestration only

**DO NOT implement code yourself.** Your job is to:
1. Check the current phase in `STATE.yaml`
2. Run the `cclab gen impl-change` command

The actual implementation is done by a **separate Claude session** spawned by the command. This session has access to the proposal specs and implements according to `tasks.md`.

You are a dispatcher, not an implementer. Run the command and let the subprocess handle the work.

**Note**: `cclab gen impl-change` is state-aware and automatically runs the full workflow:
- Implementation (Claude writes code + tests)
- Review (Codex runs tests + security scan)
- Resolve loop (if NEEDS_CHANGES, up to max iterations)

There are NO separate `review` or `resolve-reviews` commands anymore.

## Usage

```bash
/cc:gen:impl-change <change-id>
```

## Example

```bash
/cc:gen:impl-change add-oauth
```

## How it works

The skill determines readiness based on the `phase` field in `STATE.yaml`:

| Phase | Action |
|-------|--------|
| `planned` | ✅ Run `cclab gen impl-change` - starts full workflow |
| `implementing` | ✅ Run `cclab gen impl-change` - resumes from review step |
| `implemented` | ℹ️ Already done, ready to archive |
| Other phases | ❌ **ChangeNotReady** error - not ready for implementation |

**Note**: The `cclab gen impl-change` command is **state-aware** and automatically determines what to do:
- If `planned`: Start implementation → review → resolve loop
- If `implementing` with no REVIEW.md: Run review step
- If `implementing` with REVIEW.md: Check verdict and resolve if needed
- If `implemented`: Display success message

No manual intervention needed between steps!

## Prerequisites

- Change must have passed challenge (phase: `planned`)
- All planning artifacts must exist:
  - `proposal.md`
  - `tasks.md`
  - `specs/*.md`

## Knowledge Reference

Before implementation, the spawned session may consult `genesis/knowledge/` for:
- Existing patterns and conventions
- Module-specific implementation details
- Architecture constraints

Use `cclab gen knowledge read <path>` CLI command to access documentation.

## State transitions

```
planned → implementing → implemented
           ↗ (NEEDS_FIX - auto-fix)
```

## IMPORTANT: Do NOT archive automatically

After implementation completes, **stop and report success**.
Do NOT run `/cc:gen:merge-change` automatically.
The user must explicitly request archiving.

## Next steps

- **If implemented**: Inform user that implementation is done. They can run `/cc:gen:merge-change <change-id>` when ready
- **If failed**: Review `IMPLEMENTATION.md` and `REVIEW.md` for errors

## Error: ChangeNotReady

This error occurs when trying to implement before the proposal is approved:

```
❌ ChangeNotReady: Change must be in 'planned' or 'implementing' phase

Current phase: drafting
Action required: Complete planning first with /cc:gen:plan-change <change-id>
```

**Resolution**: Complete the planning workflow first using `/cc:gen:plan-change`.