ready-to-implement

# Ready to Implement

## Collab Session Required

Before proceeding, check for active collab session:

1. Check if `.collab/` directory exists
2. Check if any session folders exist within
3. If no session found:
   ```
   No active collab session found.

   Use /collab to start a session first.
   ```
   **STOP** - do not proceed with this skill.

4. If multiple sessions exist, check `COLLAB_SESSION_PATH` env var or ask user which session.

## Overview

Validates that all work items are documented and transitions from brainstorming to implementation phase.

**Core principle:** No implementation without complete work item documentation.

**Announce at start:** "I'm using the ready-to-implement skill to validate design completion."

## When to Use

Use this skill when:
- Work item loop is complete and you want to verify all items are documented
- Resuming a session (collab skill always routes through here)
- You want to transition from brainstorming to rough-draft phase

## When NOT to Use

Do NOT use this skill when:
- No collab session is active (use `/collab` first)
- Design document does not exist yet (use `/collab` to start a session)
- Already in implementation phase (use `/executing-plans` instead)

## Behavior

1. Find active collab session
2. Read design document
3. Parse Work Items section for "### Item N:" sections
4. Check each item's Status field (pending vs documented)
5. If pending items exist: list them and return to work item loop
6. If all documented: show summary and ask user confirmation
7. On confirm: update state.phase to "rough-draft/interface" and invoke rough-draft

## Implementation

When invoked, follow these steps:

### Step 1: Find Active Session

```bash
# List collab sessions
ls -d .collab/*/ 2>/dev/null | xargs -I{} basename {}
```

If no sessions exist, report: "No active collab sessions found."

If multiple sessions exist, ask user which session to check.

### Step 2: Read Design Document

Use the MCP tool to get the design document: