メニュー
[DEPRECATED — use $nmg-sdlc:upgrade-project instead] This skill was renamed in nmg-sdlc 1.42.0. Invoking $nmg-sdlc:migrate-project prints a deprecation notice pointing to $nmg-sdlc:upgrade-project and exits. Will be removed in the next minor release.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interview user about a feature need, create groomed GitHub issue with BDD acceptance criteria. Use when user says 'create issue', 'new feature', 'report a bug', 'log a bug', 'request a feature', 'I need a...', 'file an issue', 'draft an issue', 'how do I create an issue', or 'how to file a feature request'. Do NOT use for writing specs, implementing code, or creating PRs. Supports feature and bug templates with codebase investigation and milestone assignment. First step in the SDLC pipeline — followed by $nmg-sdlc:start-issue.
Initialize a project for the SDLC: bootstrap greenfield projects with steering interview, VERSION + manifest setup, v1 milestone seeding, and starter issues via $nmg-sdlc:draft-issue; or reconcile brownfield specs from closed issues, merged PR diffs, and the current source tree. Use when user says 'onboard project', 'bootstrap project', 'initialize project', 'adopt nmg-sdlc', 'set up nmg-sdlc', 'I need specs for an existing codebase', or 'reconcile specs from history'. Do NOT use for new feature specs (use $nmg-sdlc:write-spec), template upgrades (use $nmg-sdlc:upgrade-project), or issue/PR creation. Delegates to $nmg-sdlc:init-config, $nmg-sdlc:upgrade-project, and $nmg-sdlc:draft-issue where appropriate. Pipeline position: runs once per project lifetime, before $nmg-sdlc:draft-issue.
Upgrade a project to the latest nmg-sdlc contract — relocate legacy `.codex/steering/` and `.codex/specs/` to the project root, update specs, steering docs, and configs to current template standards. Use when user says 'upgrade project', 'update templates', 'check for outdated docs', 'sync with latest plugin', 'relocate specs', 'how do I update my project', or 'bring my project up to date'. Detects the legacy `.codex/{steering,specs}` directory layout and migrates it in place via `git mv`, then diffs headings against current templates and merges missing sections while preserving all user content. Utility skill — run after plugin updates, outside the main SDLC pipeline.
Verify implementation against spec, fix findings, review architecture and test coverage, update GitHub issue. Use when user says 'verify specs', 'check implementation', 'review the code against spec', 'validate the code', 'check if done', 'run verification for #N', 'how do I verify the implementation', 'how to check if the feature is done', or 'is this ready to merge'. Do NOT use for writing specs, implementing code, or creating PRs. Includes SOLID/security/performance review, exercise testing for plugin changes, and auto-fix of findings. Fifth step in the SDLC pipeline — follows $nmg-sdlc:write-code and precedes $nmg-sdlc:open-pr.
Read specs for current branch, enter plan mode, then execute implementation tasks sequentially. Use when user says 'implement the spec', 'start coding', 'build the feature', 'implement issue #N', 'resume implementation', 'how do I implement this', 'how to start coding', 'write the code', or 'build it'. Do NOT use for writing specs, verifying implementations, or creating PRs. Reads requirements, design, and tasks from specs/ and executes them in order. Fourth step in the SDLC pipeline — follows $nmg-sdlc:write-spec and precedes $nmg-sdlc:verify-code.
Create BDD specifications from a GitHub issue: requirements, technical design, and task breakdown. Use when user says 'write specs', 'create specifications', 'spec this issue', 'spec #N', 'formalize requirements', 'how do I write specs', 'how to spec a feature', 'design this feature', or 'plan the implementation'. Do NOT use for creating issues, implementing code, or verifying implementations. Produces requirements.md, design.md, tasks.md, and feature.gherkin with human review gates. Third step in the SDLC pipeline — follows $nmg-sdlc:start-issue and precedes $nmg-sdlc:write-code.
| name | migrate-project |
| description | [DEPRECATED — use $nmg-sdlc:upgrade-project instead] This skill was renamed in nmg-sdlc 1.42.0. Invoking $nmg-sdlc:migrate-project prints a deprecation notice pointing to $nmg-sdlc:upgrade-project and exits. Will be removed in the next minor release. |
Read ../../references/codex-tooling.md when the workflow starts — it maps legacy tool wording to Codex-native file inspection, shell, editing, web, interactive-gate, and subagent behavior.
Read ../../references/interactive-gates.md when the workflow reaches any manual-mode user decision, menu, review gate, or clarification prompt — Codex asks through request_user_input in Plan Mode, then finalizes a <proposed_plan> before execution.
This skill has been renamed to
$nmg-sdlc:upgrade-projectas of nmg-sdlc 1.42.0.The rename reflects the skill's primary job — bringing a project forward to match the current plugin contract, not just "migrating" isolated artifacts.
Run
$nmg-sdlc:upgrade-projectinstead. It performs everything the old$nmg-sdlc:migrate-projectdid, plus the new legacy-layout relocation (.codex/steering/→steering/and.codex/specs/→specs/) required by current Codex releases.This deprecation stub will be removed in the next minor release. Update any automation, documentation, or muscle memory to use
$nmg-sdlc:upgrade-project.
| Old | New |
|---|---|
$nmg-sdlc:migrate-project | $nmg-sdlc:upgrade-project |
.codex/migration-exclusions.json | .codex/upgrade-exclusions.json (auto-migrated on first $nmg-sdlc:upgrade-project run) |
Analyzed .codex/steering/ and .codex/specs/ | Analyzes steering/ and specs/ at the project root; relocates legacy .codex/{steering,specs} in Step 1.5 |
Stop here. Print the notice above to the user. Do not attempt to perform any upgrade work from this stub — direct the user to $nmg-sdlc:upgrade-project and exit.
This deprecated compatibility stub is outside the SDLC pipeline. Use $nmg-sdlc:upgrade-project for project contract upgrades before running pipeline skills.
