rough-draft

## 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.

# Rough-Draft: From Design to Implementation

## RESTRICTIONS

**FORBIDDEN during rough-draft phase:**
- Edit tool on source files (only allowed in `.collab/` folder)
- Write tool on source files (only allowed in `.collab/` folder)
- Any file modification outside `.collab/` folder
- Implementing code directly (must go through executing-plans)

**ALLOWED during rough-draft:**
- MCP collab tools - **prefer patch operations** for efficiency:
  - `patch_document` for targeted edits (status changes, adding fields)
  - `patch_diagram` for small diagram updates
  - `update_document`/`update_diagram` only for large rewrites or new sections
  - `create_diagram`, `create_document` for new artifacts
- Read tool (for exploration and context)
- Bash tool (for non-destructive commands like `ls`, `git status`)

**Why this matters:**
- Editing source files during rough-draft bypasses executing-plans
- This skips TDD, spec compliance, and code review gates
- All implementation MUST go through executing-plans with subagent dispatch

**RED FLAG:** If you're about to use Edit or Write on a source file, STOP. You're in the wrong phase. Document changes in the design doc and wait for executing-plans.

---

## Overview

The rough-draft skill bridges the gap between brainstorming (design) and implementation. It progressively refines the design through 4 phases, with verification gates at each transition to catch drift early.

```
+--------------+     +--------------+     +--------------+     +--------------+
|  Interface   |---->|  Pseudocode  |---->|   Skeleton   |---->|  I