Gwt Spec To Issue Migration
Productivitygwt-spec-to-issue-migrationGwt Spec To Issue Migration is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Migrate existing local SPEC directories (specs/SPEC-*) to GitHub Issue-first specs (gwt-spec label) using the bundled migration script. Use when asked to replace local spec.md/plan.md/tasks.md based workflow with GitHub Issue based management.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/gwt-spec-to-issue-migration-akiojin-llmlb-2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gwt-spec-to-issue-migration, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
gwt Spec to Issue Migration
Overview
Use this skill only for repositories that still carry legacy local spec trees from a pre-Issue-first workflow.
Migrate local specs/SPEC-* directories to GitHub Issues (gwt-spec label), then remove the legacy local source of truth.
This skill uses:
.claude/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.shcrates/gwt-core/src/git/issue_spec.rs
Preconditions
- Run in repository root
gh auth statusis authenticated for target repo- Branch policy is respected (no branch creation/switching unless user requests)
$GWT_PROJECT_ROOTenvironment variable is available; prefer it over CWD for repo resolution
Standard Workflow
- Inspect source specs directory (auto-detection or explicit
--specs-dir) - Run dry-run and review planned migration count and deletion targets
- Run actual migration
- Verify migrated issues exist (
gwt-speclabel) - Confirm legacy local spec files were removed on success
Commands
Dry-run
bash ".claude/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh" --dry-run
Dry-run with explicit specs directory
bash ".claude/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh" --dry-run --specs-dir "<path-to-specs>"
Execute migration
bash ".claude/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh"
Verify report
cat migration-report.json
Note: migration-report.json is deleted automatically after a fully successful migration cleanup. It remains available for dry-run and failure cases.
Verify created issues
gh issue list --label gwt-spec --state all --limit 200
Expected Behavior
- Auto-detects local
specs/under$GWT_PROJECT_ROOTor the current repository - If no
SPEC-*directory exists, exits successfully with empty report ([]) - Migrates sections from
spec.md,plan.md,tasks.mdand related artifacts - Writes per-spec result to
migration-report.json - Shows planned deletions during
--dry-run - Deletes migrated local spec directories, detected legacy workflow leftovers, and
migration-report.jsonafter a fully successful cleanup
Notes
- For safety, always run
--dry-runfirst. - Artifact files in
contracts/andchecklists/are migrated as issue comments. - After migration, ongoing spec updates should use Issue-first operations (
gwt-spec-ops). - This skill is for external legacy import only; gwt's normal spec workflow should never recreate repository-local spec bundles.