Legacy Flow Skill Migration

<!-- xid: C5E2A7D19F84 -->
<a id="xid-C5E2A7D19F84"></a>

# Skill: legacy_flow_skill_migration

## Purpose

Analyze a Flow / Skill created on an older XRefKit state and generate a
current trial-first migration scaffold.

Use the canonical rules in
`knowledge/operations/130_legacy_flow_skill_migration_rules.md#xid-7B3E5D1A6104`.

## Required Knowledge (XID)

- [Context direction guard rules](../../../knowledge/organization/160_context_direction_guard_rules.md#xid-7A2F4C8D1601)
- [Legacy Flow / Skill migration rules](../../../knowledge/operations/130_legacy_flow_skill_migration_rules.md#xid-7B3E5D1A6104)
- [Legacy Flow / Skill migration guide](../../../docs/guides/062_legacy_flow_skill_migration_guide.md#xid-E3B7D5A18C62)

## Optional References

- [Legacy Flow / Skill migration template](references/legacy_flow_skill_migration_template.md#xid-9DD40488BB9D)

## Inputs

- source folder or exported artifact from an older XRefKit state
- optional target skill id
- optional report output path

## Outputs

- migration report
- source inventory
- old-to-new mapping table
- current `meta` scaffold
- explicit migration gaps

## Startup

- Confirm source artifact location exists.
- Confirm whether the source is:
  - older checkout folder
  - exported skill folder
  - copied flow/skill bundle
- Load migration rules and template.

## Planning

- Inventory source files such as:
  - `SKILL.md`
  - `meta.md`
  - flow docs
  - YAML workflow control
  - nearby domain/reference files
- Identify the candidate target skill id.
- Classify content into:
  - execution procedure
  - factual/domain content
  - workflow explanation
  - workflow control
  - runtime assumptions
- Identify migration gaps.

## Execution

1. Produce a source inventory.
2. Produce an old-to-new mapping table.
3. Generate a current `meta` scaffold that defaults to `trial`.
4. Record explicit migration gaps.
5. If using the helper tool, run:

```powershell
python tools/migrate_legacy_flow_skill.py --source-dir <old-skill-dir> --out-dir <workspace-or-target-dir>
```

6. Use the template in
   `references/legacy_flow_skill_migration_template.md` or equivalent
   structure.

## Monitoring and Control

- Downgrade any unsupported mapping into an explicit gap.
- Do not claim `flows/` output unless a real machine-readable control structure
  exists.
- Do not claim `stable` readiness from old artifacts alone.
- Keep mixed procedure/fact content visible until split.

## Closure

- Return report paths and scaffold paths.
- Return migration gaps.
- Return the smallest next step, such as:
  - split facts from procedure
  - move workflow explanation to docs
  - add current meta fields
  - validate trial readiness

## Rules

- Do not overwrite current canonical assets blindly.
- Do not erase legacy intent while normalizing structure.
- Default to `trial`, not `stable`.
- Keep migration evidence and unresolved gaps explicit.

## Reporting Contract (共通報告)



- reporting_profile: summary_first

Use the shared [Skill Reporting Contract](../../../docs/core/contracts/081_skill_reporting_contract.md#xid-6B2D9F4A1C73) in the final report. Start with these headings in this order:

1. Status — done, partial, blocked, or escalated
2. Result — what was produced or decided
3. Evidence — output, evidence, checks, or XIDs
4. Open Items — unresolved unknowns, risks, judgments, or なし
5. Handoff — next owner and next action, or なし

Keep this summary-first section visible before Skill-specific detail; do not omit empty sections.