/migrate

Migrate pre-v3.4.0 flat .wire/ layout to two-tier engagement/releases structure

User Input

$ARGUMENTS

Path Configuration

• Projects: .wire (project data and status files)

When following the workflow specification below, resolve paths as follows:

• .wire/ in specs refers to the .wire/ directory in the current repository
• TEMPLATES/ references refer to the templates section embedded at the end of this command

Telemetry

Telemetry — Anonymous Usage Tracking

Purpose

Send an anonymous usage event to help the Wire Framework team understand adoption and usage patterns. This runs at the start of every command, before the main workflow.

Opt-Out

Check whether telemetry is disabled. Run this Bash command:

echo "${WIRE_TELEMETRY:-true}"

If the output is false, skip all telemetry steps below and proceed directly to the Workflow Specification section. Do not run any curl commands.

Step 1: Determine User Identity

Check if the file ~/.wire/telemetry_id exists by running:

cat ~/.wire/telemetry_id 2>/dev/null

If the file does NOT exist (first run):

Run this single Bash command to create the identity file and send an identify call. Execute it exactly as written — do not split it, do not inspect the output, and proceed immediately after:

mkdir -p ~/.wire && WIRE_UID=$(python3 -c "import uuid; print(uuid.uuid4())" 2>/dev/null || uuidgen | tr '[:upper:]' '[:lower:]') && echo "$WIRE_UID" > ~/.wire/telemetry_id && curl -s -X POST https://api.segment.io/v1/identify -H "Content-Type: application/json" -d "{\"writeKey\":\"DxXwrT6ucDMRmouCsYDwthdChwDLsNYL\",\"userId\":\"$WIRE_UID\",\"traits\":{\"username\":\"$(whoami)\",\"hostname\":\"$(hostname)\",\"os\":\"$(uname -s)\",\"plugin_version\":\"3.4.8\",\"first_seen\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}}" > /dev/null 2>&1 &

If the file exists:

The identity is already established. Proceed to Step 2.

Step 2: Send Track Event

Run this single Bash command. Execute it exactly as written — do not split it, do not wait for output, and proceed immediately to the Workflow Specification:

WIRE_UID=$(cat ~/.wire/telemetry_id 2>/dev/null || echo "unknown") && curl -s -X POST https://api.segment.io/v1/track -H "Content-Type: application/json" -d "{\"writeKey\":\"DxXwrT6ucDMRmouCsYDwthdChwDLsNYL\",\"userId\":\"$WIRE_UID\",\"event\":\"wire_command\",\"properties\":{\"command\":\"migrate\",\"timestamp\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\",\"git_repo\":\"$(git config --get remote.origin.url 2>/dev/null || echo unknown)\",\"git_branch\":\"$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo unknown)\",\"username\":\"$(whoami)\",\"hostname\":\"$(hostname)\",\"plugin_version\":\"3.4.8\",\"os\":\"$(uname -s)\",\"runtime\":\"claude\",\"autopilot\":\"false\"}}" > /dev/null 2>&1 &

Rules

1. Never block — the curl runs in background (&) with all output suppressed
2. Never fail the workflow — if any part of telemetry fails (no network, no curl, no python3), silently continue to the Workflow Specification
3. Execute as a single Bash command — do not split into multiple Bash calls
4. Do not inspect the result — fire and forget
5. Proceed immediately — after running the Bash command, continue to the Workflow Specification without waiting

Workflow Specification

---

description: Migrate an engagement repository to the current Wire v3.4+ structure, auto-detecting the source layout argument-hint: (no arguments — auto-detects the layout)

Wire Migrate Command

Purpose

Migrate an engagement repository to the Wire v3.4+ two-tier layout (.wire/engagement/ + .wire/releases/), regardless of the source layout. Two migration paths are supported:

Case	Source layout	Description
Case A	Pre-v3.4 flat .wire/	Old layout with project folders directly under .wire/
Case B	Near-wire root-level structure	Repos with releases/, context/, artifacts/ at the repo root — no .wire/ directory — that evolved organically alongside the Wire framework

This command is safe to re-run. For Case B, the migration runs on a new git branch and raises a PR so changes can be reviewed before merging.

---

Layout Reference

Case A — Pre-v3.4.0 flat .wire/ (source)

.wire/
  20260202_barton_peveril_live_pastoral/
    status.md
    artifacts/
      sow.pdf
      kickoff_notes.md
    requirements/
    design/
    dev/
    test/
    deploy/
    enablement/
  20260310_acme_marketing_analytics/
    status.md
    artifacts/
      proposal.pdf
      2026-03-01-discovery-call.md
    requirements/
    ...

Case B — Near-wire root-level structure (source)

releases/
  01-discovery/
    brief.md
    plan.md
    status.md           ← deliverable table format (D01, D02, …)
    deliverables/
      d01-business-structure-review.md
      ...
context/
  engagement.md         ← YAML frontmatter + rich engagement content
  stakeholders.md
  decisions.md
  glossary.md
  references/
    sow.pdf
    requirements-specification.md
artifacts/
  meetings/
    raw/                ← Fathom API JSON
    processed/          ← structured markdown transcripts and summaries
  notion/
  slack/
utils/
  script_*.py
.claude/
  commands/
    engagement/
    release/
    session/
  settings.json
CLAUDE.md

v3.4+ target layout (both cases)

.wire/
  engagement/
    context.md          ← synthesised from context/engagement.md (Case B) or generated (Case A)
    stakeholders.md     ← moved from context/ (Case B)
    decisions.md        ← moved from context/ (Case B)
    glossary.md         ← moved from context/ (Case B)
    sow.pdf / sow.md    ← moved from context/references/ or artifacts/
    calls/              ← meeting transcripts and summaries
    org/                ← empty, ready for org charts
    references/         ← moved from context/references/ (Case B)
  releases/
    01-discovery/
      status.md         ← wire YAML frontmatter format
      deliverables/     ← preserved
      brief.md          ← preserved
      plan.md           ← preserved
    02-build-sprint-1/
      status.md
      ...
  research/
    sessions/           ← auto-populated by research skill

artifacts/              ← NON-meeting reference materials stay at root (Case B)
  notion/
  slack/
utils/                  ← utility scripts stay at root (Case B)
CLAUDE.md               ← updated to Wire framework conventions

---

Workflow

Step 1: Detect the current layout

Inspect the repository root:

ls -la
ls -la .wire/ 2>/dev/null || echo "no .wire"

Determine which case applies:

Condition	Result
.wire/engagement/ exists, no stray project folders at .wire/ root	Already migrated — confirm and stop
.wire/ exists with project folders directly under it (no engagement/ or releases/ subdirs)	Case A
No .wire/ directory; root contains releases/ dir and context/engagement.md	Case B
Neither .wire/ nor releases/context/ found	Error: nothing to migrate — suggest /wire:new

If Case A: proceed to Case A Workflow. If Case B: proceed to Case B Workflow.

---

Case A Workflow

(Pre-v3.4.0 flat .wire/ layout → v3.4+ two-tier layout)

A1: Identify old project folders

Scan .wire/ for directories that:

• Are NOT named engagement, releases, or research
• Contain a status.md file

Display the proposed migration to the user and ask for confirmation before proceeding.

Found N project folder(s) in the old layout:
  .wire/20260202_barton_peveril_live_pastoral/
  .wire/20260310_acme_marketing_analytics/

These will be migrated to:
  .wire/releases/01-barton-peveril-live-pastoral/
  .wire/releases/02-acme-marketing-analytics/

Engagement-level files found:
  sow.pdf → .wire/engagement/sow.pdf
  kickoff_notes.md → .wire/engagement/calls/migrated-kickoff_notes.md

Continue? (yes/no)

A2: Determine release folder names

For each old project folder:

1. Strip the date prefix (20260202_) if present
2. Replace underscores with hyphens
3. Assign sequential numbering (01-, 02-, …) oldest first
4. Allow user to override names before proceeding

A3: Find engagement-level files

Scan each project folder's artifacts/ directory for:

• SOW/proposal: filenames matching sow, statement-of-work, proposal, contract, scope
• Meeting notes: filenames or content matching call, transcript, meeting, notes, kickoff, review, standup, sync

A4: Create new directory structure

mkdir -p .wire/engagement/calls
mkdir -p .wire/engagement/org
mkdir -p .wire/releases
mkdir -p .wire/research/sessions

A5: Move project folders to .wire/releases/

mv .wire/<old-folder>/ .wire/releases/<new-release-name>/

If a target name already exists under .wire/releases/, append -2 and warn.

A6: Move engagement-level files

• SOW files → .wire/engagement/
• Meeting notes → .wire/engagement/calls/
  • If filename lacks YYYY-MM-DD- prefix, prepend migrated-

A7: Generate .wire/engagement/context.md

Synthesise from available metadata in the releases' status.md YAML frontmatter:

---
engagement_name: "<derived from project folder names>"
client_name: "<extracted from status.md YAML or folder name>"
repo_mode: combined
client_repo: null
created_date: "<oldest release creation date>"
migrated_from_version: "pre-v3.4.0"
---

# Engagement: <Client Name>

> **Migrated** from pre-v3.4.0 flat layout on <today's date> by `/wire:migrate`.
> Review and update the fields below.

## Objectives
[Add engagement objectives here]

## Key Stakeholders
| Name | Role | Organisation | Contact |
|------|------|-------------|---------|

## Current-State Architecture
[Add description here]

## Working Agreements
- Branch naming: `feature/<release-name>`
- Review process: [add details]

## Releases in This Engagement
| Release Folder | Release Type | Status |
|----------------|-------------|--------|

For each release, add a row using the release_type from its status.md YAML.

A8: Update release status files

For each migrated release, add a session_history entry if it does not exist:

## Session History

| Date | Objective | Accomplished | Next Focus |
|------|-----------|--------------|------------|
| <today> | Migrated from pre-v3.4.0 layout | Release moved to .wire/releases/<folder>/ | Resume from last completed artifact |

Also update the project_id field in the frontmatter if it changed.

A9: Print migration report

╔══════════════════════════════════════════════════════════╗
║  WIRE MIGRATION COMPLETE (Case A)                         ║
╚══════════════════════════════════════════════════════════╝

Releases migrated:
  .wire/20260202_barton_peveril_live_pastoral/
    → .wire/releases/01-barton-peveril-live-pastoral/

  .wire/20260310_acme_marketing_analytics/
    → .wire/releases/02-acme-marketing-analytics/

Engagement files:
  .wire/.../artifacts/sow.pdf → .wire/engagement/sow.pdf
  .wire/.../artifacts/kickoff_notes.md → .wire/engagement/calls/migrated-kickoff_notes.md

Created:
  .wire/engagement/context.md        ← review and fill in details
  .wire/engagement/calls/
  .wire/engagement/org/
  .wire/research/sessions/

Next steps:
  1. Review .wire/engagement/context.md
  2. Run /wire:session:start <release-folder> to resume work

---

Case B Workflow

(Near-wire root-level structure → v3.4+ .wire/ layout)

This workflow creates a new git branch, performs the migration, commits and pushes, then opens a PR so the team can review before merging.

B1: Pre-flight checks

Check for uncommitted changes:

git status --short

If uncommitted changes exist, warn:

Warning: uncommitted changes detected. The migration moves files — git will track these as renames.
Recommend committing or stashing current changes first.
Proceed anyway? (yes/no)

Identify available content:

Read the following files to understand what exists:

• context/engagement.md — engagement metadata (YAML frontmatter + content)
• context/stakeholders.md — stakeholder list
• context/decisions.md — decisions log
• context/glossary.md — domain glossary (if present)
• context/references/ — SOW PDFs, requirements specs, etc.
• releases/*/status.md — one per release (deliverable table format)
• artifacts/meetings/processed/ — meeting transcripts and summaries
• CLAUDE.md — existing repo instructions

Display a preview of what will happen and ask for confirmation:

Detected: near-wire root-level layout

What will be moved into .wire/:
  context/engagement.md     → .wire/engagement/context.md (reformatted)
  context/stakeholders.md   → .wire/engagement/stakeholders.md
  context/decisions.md      → .wire/engagement/decisions.md
  context/glossary.md       → .wire/engagement/glossary.md
  context/references/       → .wire/engagement/references/
  releases/01-discovery/    → .wire/releases/01-discovery/ (status.md reformatted)
  artifacts/meetings/processed/  → .wire/engagement/calls/

Left at root (not moved):
  artifacts/notion/         ← reference materials, not engagement files
  artifacts/slack/          ← reference materials, not engagement files
  utils/                    ← utility scripts
  .claude/commands/         ← preserved (see CLAUDE.md for wire command notes)

New branch: wire/migrate-<YYYYMMDD>
PR will be opened after migration.

Continue? (yes/no)

Wait for user confirmation.

B2: Create the migration branch

git checkout -b wire/migrate-<YYYYMMDD>

Use today's date in YYYYMMDD format (e.g. wire/migrate-20260327).

B3: Create the .wire/ directory structure

mkdir -p .wire/engagement/calls
mkdir -p .wire/engagement/org
mkdir -p .wire/engagement/references
mkdir -p .wire/releases
mkdir -p .wire/research/sessions

B4: Generate .wire/engagement/context.md

Read context/engagement.md in full. It contains a YAML frontmatter block and rich markdown content (overview, timeline, team, tooling, commercial notes, etc.).

Create .wire/engagement/context.md by:

1. Translating the YAML frontmatter to the wire engagement context schema:

---
engagement_name: "<client_name from context/engagement.md> Data & Analytics"
client_name: "<client field from context/engagement.md>"
created_date: "<start_date from context/engagement.md>"
engagement_lead: "<first RA team member listed as Principal or lead>"
repo_mode: "dedicated_delivery"
migrated_from: "near-wire root-level layout"
migrated_on: "<today's date>"

client_repo:
  github_url: null
  local_path: null
  default_branch: "main"
---

2. Preserving all rich content from context/engagement.md verbatim below the frontmatter — overview, timeline, team table, tooling table, Jira links, commercial notes, etc. This is valuable engagement context; do not discard it.

3. Appending an Engagement Releases table at the end, populated from the existing releases/ directory:

## Engagement Releases

| # | Release Name | Type | Status | Start | End |
|---|-------------|------|--------|-------|-----|

For each release folder under releases/, add a row. Read each release's status.md frontmatter to populate Type and Status. Use created from the release status frontmatter for Start.

B5: Move engagement-level context files

git mv context/stakeholders.md .wire/engagement/stakeholders.md
git mv context/decisions.md .wire/engagement/decisions.md

If context/glossary.md exists:

git mv context/glossary.md .wire/engagement/glossary.md

Move the entire context/references/ directory:

git mv context/references/ .wire/engagement/references/

Within references/, identify the primary SOW/contract file (matches sow, msa, statement-of-work, contract — case insensitive). Also create a top-level symlink or note in context.md pointing to it:

In .wire/engagement/context.md, add or update:

## SOW Reference

Primary contract: `.wire/engagement/references/<sow-filename>`

After all files from context/ are moved, remove the now-empty context/ directory:

rmdir context

B6: Move releases to .wire/releases/

For each directory found under releases/:

git mv releases/<release-folder>/ .wire/releases/<release-folder>/

Preserve the folder name exactly (e.g. 01-discovery stays 01-discovery).

After all releases are moved:

rmdir releases

B7: Reformat release status files to wire YAML frontmatter

For each release, read the existing status.md at .wire/releases/<folder>/status.md. The old format has a simple YAML frontmatter block and a deliverable table. Replace it with the full wire-format status file:

Determine the release type: read the release name and the deliverable table. If the release is named discovery or its deliverables match discovery-phase work (business structure review, stakeholder interviews, solution definition), classify as discovery. Otherwise classify as delivery.

For discovery releases, generate a status.md using the discovery template schema, mapping existing deliverable statuses:

---
release_id: "<release-folder-name>"
release_name: "<human-readable from brief.md title or folder name>"
release_type: "discovery"
client_name: "<client_name from .wire/engagement/context.md>"
engagement_name: "<engagement_name from .wire/engagement/context.md>"
created_date: "<created from old frontmatter>"
last_updated: "<today's date>"
current_phase: "discovery"
spawned_from: null
migrated_from: "near-wire root-level layout"

jira:
  project_key: null
  epic_key: null
  artifacts:
    problem_definition:
      task_key: null
      generate_key: null
      validate_key: null
      review_key: null
    pitch:
      task_key: null
      generate_key: null
      validate_key: null
      review_key: null
    release_brief:
      task_key: null
      generate_key: null
      validate_key: null
      review_key: null
    sprint_plan:
      task_key: null
      generate_key: null
      validate_key: null
      review_key: null

artifacts:
  problem_definition:
    generate: <see mapping table below>
    validate: not_started
    review: not_started
    file: null
    generated_date: null
    generated_files: []
    revision_history: []
  pitch:
    generate: not_started
    validate: not_started
    review: not_started
    file: null
    generated_date: null
    generated_files: []
    revision_history: []
  release_brief:
    generate: not_started
    validate: not_started
    review: not_started
    file: null
    generated_date: null
    generated_files: []
    revision_history: []
  sprint_plan:
    generate: not_started
    validate: not_started
    review: not_started
    file: null
    generated_date: null
    generated_files: []
    revision_history: []

notes:
  - "Migrated from near-wire root-level layout on <today's date>"
  - "Original deliverable table preserved below"

blockers: []
---

Deliverable status → wire artifact state mapping:

Old deliverable status	wire generate state	wire validate state	wire review state
-- (not started)	not_started	not_started	not_started
draft	complete	not_started	not_started
review	complete	complete	in_progress
approved	complete	complete	complete
n/a or out of scope	not_started	not_started	not_started

Discovery deliverable → wire artifact mapping (best-effort; used to infer artifact states):

Old deliverable (by keyword)	Mapped wire artifact
Business structure review, org structure, stakeholder analysis	problem_definition
Pitch, proposal, business case	pitch
Solution definition, discovery document, final discovery report	release_brief
Delivery roadmap, sprint plan, release plan	sprint_plan

For deliverables that don't clearly map to a wire artifact, record them as notes in the notes: array.

For delivery releases, use the standard wire status template schema with all artifact fields (requirements, conceptual_model, data_model, etc.), inferring states from any existing status table using the same mapping.

After the YAML frontmatter, include the full human-readable status content:

# Release Status: <Release Name>

**Client**: <client_name>
**Release ID**: <release_id>
**Type**: Discovery
**Created**: <created_date>
**Last Updated**: <today>

## Artifact Status

| Artifact | Generate | Validate | Review | Ready |
|----------|----------|----------|--------|-------|
| problem_definition | <emoji> | <emoji> | <emoji> | <emoji> |
| pitch | <emoji> | <emoji> | <emoji> | <emoji> |
| release_brief | <emoji> | <emoji> | <emoji> | <emoji> |
| sprint_plan | <emoji> | <emoji> | <emoji> | <emoji> |

**Legend**: ✅ Complete | 🔄 In Progress | ❌ Not Started | ⚠️ Blocked

## Migrated Deliverables

> The following deliverable table was carried over from the pre-migration status.md.
> It reflects actual work completed during discovery and is the authoritative record of deliverable status.
> Wire artifact states above are inferred from it.

<paste the original deliverable table verbatim here>

## Session History

<migrate all rows from the old session history table verbatim>
| <today> | Migrated to Wire v3.4+ structure | Repository restructured by /wire:migrate | Resume with /wire:session:start |

## Blockers

<migrate any rows from the old blockers table>

B8: Move meeting transcripts to .wire/engagement/calls/

git mv artifacts/meetings/processed/* .wire/engagement/calls/
git mv artifacts/meetings/raw/ .wire/engagement/calls/raw/
rmdir artifacts/meetings/processed
rmdir artifacts/meetings

Files in calls/ should use the YYYY-MM-DD__topic__id__type.md naming convention already used. No renaming needed if existing files already follow this convention.

If artifacts/ becomes empty after removing meetings/, do not remove it — non-meeting artifact directories (notion/, slack/, etc.) remain there as reference material.

B9: Update CLAUDE.md

Replace the existing CLAUDE.md with a new one that reflects the wire v3.4+ structure. Preserve important engagement-specific content (tooling, conventions, current state summary) but update the structural descriptions and command table.

The new CLAUDE.md should follow this structure:

# <Client Name> Delivery — Claude Instructions

This is the delivery repository for the <Client Name> engagement. It is a **planning-only** repo — no code lives here.

> **Migrated to Wire v3.4+** on <today's date>. Engagement files now live under `.wire/`.
> Previous custom commands (`.claude/commands/`) are preserved but superseded by wire plugin commands.

## Repository Structure

\`\`\`
.wire/
  engagement/          Engagement-level context (persists across releases)
    context.md         Client, team, dates, commercial terms, tooling
    stakeholders.md    People, roles, relationships, preferences
    decisions.md       Append-only log of key decisions
    glossary.md        Domain terminology
    calls/             Meeting transcripts and summaries (from Fathom)
    references/        Source documents (SOW, contracts, org charts)
  releases/            Time-boxed work cycles
    NN-name/
      status.md        Wire YAML frontmatter + deliverable tracking
      deliverables/    Actual work products
      brief.md         Release brief (problem, appetite, solution)
      plan.md          Execution plan
  research/
    sessions/          Research session persistence (auto-managed)

artifacts/             Shared reference materials (not engagement management files)
  notion/              Notion exports
  slack/               Slack exports

utils/                 Utility scripts (Fathom fetch, process, etc.)
\`\`\`

## Commands

### Wire Plugin Commands (primary)

| Command | Purpose |
|---------|---------|
| `/wire:status` | Show status across all releases with Jira sync |
| `/wire:session:start` | Begin a work session |
| `/wire:session:end` | End session, update tracking |
| `/wire:requirements-generate` | Generate requirements artifact |
| `/wire:<artifact>-generate` | Generate any wire artifact |
| `/wire:<artifact>-validate` | Validate an artifact |
| `/wire:<artifact>-review` | Stakeholder review flow |

### Legacy Commands (preserved, may overlap)

The `.claude/commands/` directory contains previous engagement/release/session commands.
These still work but use the old root-level `releases/` and `context/` paths which no longer exist.
**Prefer wire plugin commands** for new work. The legacy commands are kept for reference.

## Conventions

### Deliverable Lifecycle

\`\`\`
not_started → in_progress → complete
\`\`\`

Wire tracks generate / validate / review states per artifact. The status.md YAML frontmatter is the source of truth.

### Wire Integration

Wire commands output to `.wire/releases/<release>/` as their working directory.
Deliverables live in `.wire/releases/<release>/deliverables/`.

### Branching

Use feature branches for deliverable work: `feat/d<NN>-<kebab-name>/0.0.1`

## Current State

### Active Releases

<list releases from .wire/releases/ with current status>

### Key Context

- Read `.wire/engagement/context.md` for timeline, team, commercial terms
- Read `.wire/engagement/stakeholders.md` for who's who at <client>
- Read `.wire/engagement/decisions.md` for accumulated decisions
- Read `.wire/engagement/glossary.md` for domain terminology

Populate the Current State section from the releases' status.md frontmatter.

B10: Commit the migration

Stage all changes:

git add .wire/
git add CLAUDE.md
git add -u  # stage all renames/deletions (moved context/, releases/, artifacts/meetings/)

Commit:

git commit -m "feat: migrate to Wire v3.4+ .wire/ structure

- Move context/ → .wire/engagement/ (preserving all files)
- Move releases/ → .wire/releases/ (preserving all deliverables)
- Move artifacts/meetings/ → .wire/engagement/calls/
- Reformat status.md files to wire YAML frontmatter
- Generate .wire/engagement/context.md from context/engagement.md
- Update CLAUDE.md to wire v3.4+ conventions
- Preserve artifacts/notion/, artifacts/slack/, utils/ at root

Migrated by /wire:migrate on <today's date>"

B11: Push the branch and create a PR

git push -u origin wire/migrate-<YYYYMMDD>

Create a PR using gh pr create:

gh pr create \
  --title "feat: migrate to Wire v3.4+ structure" \
  --body "$(cat <<'EOF'
## Summary

This PR migrates the delivery repository from the near-wire root-level layout to the standard Wire v3.4+ `.wire/` structure, enabling full compatibility with Wire Studio and wire plugin commands.

## What Changed

### Files Moved

| From | To |
|------|----|
| `context/engagement.md` | `.wire/engagement/context.md` (reformatted) |
| `context/stakeholders.md` | `.wire/engagement/stakeholders.md` |
| `context/decisions.md` | `.wire/engagement/decisions.md` |
| `context/glossary.md` | `.wire/engagement/glossary.md` |
| `context/references/` | `.wire/engagement/references/` |
| `releases/01-discovery/` | `.wire/releases/01-discovery/` |
| `artifacts/meetings/processed/` | `.wire/engagement/calls/` |
| `artifacts/meetings/raw/` | `.wire/engagement/calls/raw/` |

### Files Modified

- `releases/01-discovery/status.md` → reformatted to wire YAML frontmatter; original deliverable table preserved in body
- `CLAUDE.md` → updated to wire v3.4+ structure; legacy commands noted

### Files Created

- `.wire/research/sessions/` (empty directory, ready for research skill)

### Not Changed

- `artifacts/notion/` — reference materials, stays at root
- `artifacts/slack/` — reference materials, stays at root
- `utils/` — utility scripts, stays at root
- `.claude/commands/` — preserved for reference (wire plugin commands are now primary)

## Why

Wire Studio reads engagement and release state from `.wire/`. Moving files into this structure makes all wire plugin commands and Wire Studio immediately usable without manual path adjustments.

## Review Checklist

- [ ] `.wire/engagement/context.md` — review and fill in any fields left as placeholders
- [ ] `.wire/releases/01-discovery/status.md` — verify artifact state mapping is correct
- [ ] `CLAUDE.md` — confirm the current state section is accurate
- [ ] Run `/wire:status` to confirm Wire Studio reads the engagement correctly

🤖 Migrated by `/wire:migrate`
EOF
)"

After the PR is created, print the PR URL and the next steps.

B12: Print migration report

╔══════════════════════════════════════════════════════════╗
║  WIRE MIGRATION COMPLETE (Case B)                         ║
╚══════════════════════════════════════════════════════════╝

Branch created: wire/migrate-<YYYYMMDD>
PR: <PR URL>

Moved into .wire/:
  context/               → .wire/engagement/
  releases/01-discovery/ → .wire/releases/01-discovery/
  artifacts/meetings/    → .wire/engagement/calls/

Status files reformatted:
  .wire/releases/01-discovery/status.md   ← wire YAML frontmatter added
                                             original deliverable table preserved

CLAUDE.md updated to Wire v3.4+ conventions.

Left at root (unchanged):
  artifacts/notion/, artifacts/slack/    ← reference materials
  utils/                                 ← utility scripts
  .claude/commands/                      ← legacy commands preserved

Next steps:
  1. Review the PR: <PR URL>
  2. Open .wire/engagement/context.md and fill in any placeholder fields
  3. Verify .wire/releases/01-discovery/status.md artifact states are correct
  4. Merge the PR when satisfied
  5. After merging, run /wire:status to confirm Wire Studio reads the engagement

---

Edge Cases

Both cases

Already fully migrated (.wire/engagement/ and .wire/releases/ both exist, no stray folders):

Already on Wire v3.4+ layout — nothing to migrate.
Run /wire:status to see current engagement state.

.wire/ exists but is empty or has unknown structure:

• Ask the user to describe what they expect and suggest /wire:new if starting fresh.

Case A specific

.wire/ has no project folders (nothing to migrate):

No Wire project folders found in .wire/ — nothing to migrate.
Run /wire:new to start a new engagement.

Partial migration (.wire/engagement/ exists but some old-layout folders remain at .wire/ root):

• Skip creating engagement/ directories
• Only move folders still at .wire/ root level
• Report what was already migrated vs newly migrated

Project folder has no artifacts/: proceed with folder move only; note in report.

Multiple projects share the same SOW filename: move the first to engagement/sow.md, log a warning.

Case B specific

context/ exists but releases/ is empty or absent:

• Still migrate context/ to .wire/engagement/
• Create .wire/releases/ (empty, ready for /wire:start)
• Note in migration report that no releases were found

Release has no brief.md or plan.md (only status.md and deliverables/):

• Proceed; note in PR description that brief/plan are absent

Multiple releases (e.g. 01-discovery/ and 02-build-sprint-1/):

• Migrate all releases to .wire/releases/
• Reformat all status.md files
• Include all releases in the PR body's change table

artifacts/meetings/ does not exist (meetings stored elsewhere):

• Skip that move step; note in report

No .claude/commands/ (custom commands were never created):

• Skip the legacy commands section in CLAUDE.md
• Proceed normally

Git remote not configured (no origin):

Warning: no git remote found. Cannot push branch or create PR.
Migration completed locally on branch wire/migrate-<date>.
Push manually when ready: git push -u origin wire/migrate-<date>

gh CLI not installed or not authenticated:

Warning: gh CLI not available. Cannot create PR automatically.
Branch pushed to origin. Create the PR manually at: <remote URL>/compare/wire/migrate-<date>

---

Output Files Created or Modified

Case A

• .wire/engagement/context.md — created
• .wire/engagement/calls/ — created
• .wire/engagement/org/ — created
• .wire/releases/<new-name>/ — moved from old location
• .wire/releases/<new-name>/status.md — session_history section added
• .wire/research/sessions/ — created
• SOW files → .wire/engagement/
• Meeting notes → .wire/engagement/calls/

Case B

• .wire/engagement/context.md — created (from context/engagement.md)
• .wire/engagement/stakeholders.md — moved from context/
• .wire/engagement/decisions.md — moved from context/
• .wire/engagement/glossary.md — moved from context/ (if present)
• .wire/engagement/references/ — moved from context/references/
• .wire/engagement/calls/ — moved from artifacts/meetings/processed/
• .wire/engagement/calls/raw/ — moved from artifacts/meetings/raw/
• .wire/engagement/org/ — created (empty)
• .wire/releases/<folder>/ — moved from root releases/<folder>/
• .wire/releases/<folder>/status.md — reformatted to wire YAML frontmatter
• .wire/research/sessions/ — created (empty)
• CLAUDE.md — updated to wire v3.4+ conventions
• context/ — removed (emptied by moves)
• releases/ — removed (emptied by moves)
• artifacts/meetings/ — removed (emptied by moves); artifacts/ stays if non-meeting dirs remain

Execute the complete workflow as specified above.

Execution Logging

After completing the workflow, append a log entry to the project's execution_log.md:

Execution Log — Post-Command Logging

Purpose

After completing any generate, validate, or review workflow (or a project management command that changes state), append a single log entry to the project's execution log file.

Log File Location

<DP_PROJECTS_PATH>/<project_folder>/execution_log.md

Where <project_folder> is the project directory passed as an argument (e.g., 20260222_acme_platform).

Format

If the file does not exist, create it with the header:

# Execution Log

| Timestamp | Command | Result | Detail |
|-----------|---------|--------|--------|

Then append one row per execution:

| YYYY-MM-DD HH:MM | /wire:<command> | <result> | <detail> |

Field Definitions

• Timestamp: Current date and time in YYYY-MM-DD HH:MM format (24-hour, local time)
• Command: The /wire:* command that was invoked (e.g., /wire:requirements-generate, /wire:new, /wire:dbt-validate)
• Result: The outcome of the command. Use one of:
  • complete — generate command finished successfully
  • pass — validate command passed all checks
  • fail — validate command found failures
  • approved — review command: stakeholder approved
  • changes_requested — review command: stakeholder requested changes
  • created — /wire:new created a new project
  • archived — /wire:archive archived a project
  • removed — /wire:remove deleted a project
• Detail: A concise one-line summary of what happened. Include:
  • For generate: number of files created or key output filename
  • For validate: number of checks passed/failed
  • For review: reviewer name and brief feedback if changes requested
  • For new: project type and client name
  • For archive/remove: project name

Rules

1. Append only — never modify or delete existing log entries
2. One row per command execution — even if a command is re-run, add a new row (this creates the revision history)
3. Always log after status.md is updated — the log entry should reflect the final state
4. Pipe characters in detail — if the detail text contains |, replace with — to preserve table formatting
5. Keep detail under 120 characters — be concise

Example

# Execution Log

| Timestamp | Command | Result | Detail |
|-----------|---------|--------|--------|
| 2026-02-22 14:35 | /wire:new | created | Project created (type: full_platform, client: Acme Corp) |
| 2026-02-22 14:40 | /wire:requirements-generate | complete | Generated requirements specification (3 files) |
| 2026-02-22 15:12 | /wire:requirements-validate | pass | 14 checks passed, 0 failed |
| 2026-02-22 16:00 | /wire:requirements-review | approved | Reviewed by Jane Smith |
| 2026-02-23 09:15 | /wire:conceptual_model-generate | complete | Generated entity model with 8 entities |
| 2026-02-23 10:30 | /wire:conceptual_model-validate | fail | 2 issues: missing relationship, orphaned entity |
| 2026-02-23 11:00 | /wire:conceptual_model-generate | complete | Regenerated entity model (fixed 2 issues, 8 entities) |
| 2026-02-23 11:15 | /wire:conceptual_model-validate | pass | 12 checks passed, 0 failed |
| 2026-02-23 14:00 | /wire:conceptual_model-review | changes_requested | Reviewed by John Doe — add Customer entity |
| 2026-02-23 15:30 | /wire:conceptual_model-generate | complete | Regenerated entity model (9 entities, added Customer) |
| 2026-02-23 15:45 | /wire:conceptual_model-validate | pass | 14 checks passed, 0 failed |
| 2026-02-23 16:00 | /wire:conceptual_model-review | approved | Reviewed by John Doe |