菜单
Generate an SDLC runner config for the current project. Use when user says 'generate config', 'set up SDLC runner', 'configure runner', 'init config', 'how do I set up the runner', or asks about sdlc-config.json. Creates a ready-to-use sdlc-config.json from the template with project-specific paths. Prerequisite for $nmg-sdlc:run-loop.
用 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 | init-config |
| description | Generate an SDLC runner config for the current project. Use when user says 'generate config', 'set up SDLC runner', 'configure runner', 'init config', 'how do I set up the runner', or asks about sdlc-config.json. Creates a ready-to-use sdlc-config.json from the template with project-specific paths. Prerequisite for $nmg-sdlc:run-loop. |
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.
Read ../../references/contribution-gate.md when runner config setup reaches managed project artifact creation — the shared contract defines the GitHub Actions contribution-gate workflow, managed marker/version, safe update rules, and stable status output.
Read ../../references/issue-form.md when runner config setup reaches managed issue-form installation — the shared contract defines the GitHub Issue Form path, canonical template source, overwrite rule, preservation rule, and stable status output.
Generate a ready-to-use sdlc-config.json for the SDLC runner by substituting the current project directory into the config template.
Resolve the project root — find the root of the Codex project by locating the nearest ancestor directory containing a .codex/ folder:
git rev-parse --show-toplevel
Then verify it's a Codex project:
test -d "$(git rev-parse --show-toplevel)/.codex"
If .codex/ does not exist at the repo root, stop and tell the user: this must be run from within a Codex project (a directory with .codex/ at its root).
Use this resolved project root for all subsequent steps — do NOT use pwd directly, as it may differ from the project root.
Find and read the template from the local Codex plugin checkout. Use file discovery to locate:
~/.codex/plugins/**/nmg-sdlc/**/scripts/sdlc-config.example.json
Prefer a match where skills/run-loop/SKILL.md exists under the same plugin root. If multiple versioned cache entries match, use the newest version directory. If no installed copy is found, fall back to this source checkout when it contains scripts/sdlc-config.example.json.
Derive the project name from the project root's basename:
basename "$(git rev-parse --show-toplevel)"
Resolve the plugin root — take the parent directory of the scripts/ directory that contains the template selected in Step 2. Verify this root contains both .codex-plugin/plugin.json and skills/.
Substitute values — replace the placeholder fields in the template:
"projectPath": "/path/to/your/project" → the resolved project root from Step 1"pluginRoot": "/path/to/nmg-sdlc" → the resolved plugin root, expanded to the full absolute path"pluginsPath" empty unless the local checkout uses the legacy plugins/nmg-sdlc monorepo layoutWrite the config file — save the fully substituted config JSON to sdlc-config.json in the project root (resolved in Step 1). Use Codex editing.
Add to .gitignore — ensure sdlc-config.json and .codex/sdlc-state.json are listed in the project's .gitignore:
.gitignore file in the project root. If it does not exist, create it.sdlc-config.json and .codex/sdlc-state.json: if NOT already present, add it under an # SDLC runner config comment.Install the managed contribution gate — apply ../../references/contribution-gate.md in the resolved project root:
.github/workflows/ when needed..github/workflows/nmg-sdlc-contribution-gate.yml is absent, write the managed workflow template..github/workflows/ byte-for-byte.Install the managed issue form — apply ../../references/issue-form.md in the resolved project root:
.github/ISSUE_TEMPLATE/nmg-sdlc-ready-issue.yml template from the resolved plugin root..github/ISSUE_TEMPLATE/ when needed..github/ISSUE_TEMPLATE/nmg-sdlc-ready-issue.yml is absent, write the managed form template.overwritten..github/ISSUE_TEMPLATE/ byte-for-byte.Confirm and suggest next step — tell the user the config has been written and is git-ignored, include the stable Contribution Gate status block from ../../references/contribution-gate.md and the stable Issue Form status block from ../../references/issue-form.md, then suggest:
Run the SDLC runner:
$nmg-sdlc:run-loop
Or run directly:
node scripts/sdlc-runner.mjs --config sdlc-config.json
User says: "Set up the SDLC runner for this project"
Actions: Resolves project root, reads template, substitutes paths, writes sdlc-config.json, adds to .gitignore, installs the managed contribution gate, and installs the managed issue form
Result: Config file, contribution-gate workflow, and SDLC-ready issue form ready at project root; user told how to run the runner
User says: "Generate a runner config"
Actions: Resolves project root, checks for .codex/ directory
Result: Stops with error — "This must be run from within a Codex project"
This skill is a utility for setting up the SDLC runner. It generates the configuration file that sdlc-runner.mjs reads to orchestrate the development cycle. It is not part of the SDLC cycle itself but supports the automation layer that drives it.