# Codex Group 2 Dispatch Evidence

## /create:sk-skill
- Command name: /create:sk-skill
- Fields migrated count: 9
- Tier-2 candidates identified: type, spec_choice
- Concerns: spec-linked config path is conditional; documented `/tmp/create-sk-skill-config.json` fallback when spec_choice is skip.

## /create:agent
- Command name: /create:agent
- Fields migrated count: 6
- Tier-2 candidates identified: spec_choice
- Concerns: `agent_description` appears in the argument hint but is not present in the legacy setup Q-block, so it was not added as a setup field.

## /create:changelog
- Command name: /create:changelog
- Fields migrated count: 7
- Tier-2 candidates identified: source_type, version_bump
- Concerns: `version_bump` has no legacy default despite a recommended option; table keeps it unresolved unless supplied or asked.

## /create:feature-catalog
- Command name: /create:feature-catalog
- Fields migrated count: 9
- Tier-2 candidates identified: source_strategy, spec_choice
- Concerns: `operation` has no legacy default; absence is treated as Tier 3 rather than a broad setup prompt.

## /create:testing-playbook
- Command name: /create:testing-playbook
- Fields migrated count: 9
- Tier-2 candidates identified: source_strategy, spec_choice
- Concerns: mirrors feature-catalog setup semantics with command-specific root field `playbook_root`.

## /create:folder_readme
- Command name: /create:folder_readme
- Fields migrated count: 9
- Tier-2 candidates identified: operation, readme_type, platforms, existing_file_action
- Concerns: no spec-folder setup field exists in the legacy Q-block, so the config persistence path is `/tmp/create-folder-readme-config.json`.

EXIT_STATUS: complete
