メニュー
Use when installing, updating, verifying, or adopting SpecRail for agents. Guides local Codex skill installation, global AGENTS.md guidance setup, repository adoption planning, dry-run-first verification, and explicit human authorization boundaries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.
Use when writing or updating a SpecRail product spec for a linked issue. Produces the numbered `product.md` spec from the locale-appropriate template, focusing on user-facing behavior, goals, non-goals, and acceptance criteria without implementation detail.
Use when writing or updating a SpecRail technical spec for a linked issue. Produces the numbered `tech.md` spec from the locale-appropriate template, translating accepted product behavior into design, affected files, risks, verification, and rollback without starting implementation.
Use when the user says "implx", "use implx", "用 implx", or asks for the one-line SpecRail queue shortcut. Plain implx means drain the full actionable issue/PR queue in auto mode: run SpecRail preflight, create missing spec/task PR work before implementation, use threads for reviewer/merge-reviewer lanes when available, create per-issue implementation PRs, require CI/reviewThreads/pr_gate evidence, auto-merge on complete evidence, and perform closure audit. Say "implx review" / "implx 人工" for the review mode that keeps per-PR human merge authorization.
Use when implementing or draining a GitHub issue/PR queue in a SpecRail-governed repository where approved specs already exist, such as multiple numbered specs/GH packets that need one or more implementation PRs per issue. Maps issues to specs and existing PRs, supports full-queue drain requests from implx, selects single-agent or optional threads orchestration, preserves partial versus final closing semantics, and requires SpecRail verification plus PR gates before merge-readiness claims.
Use before reporting a SpecRail PR as merge-ready. Collects read-only PR evidence, runs the offline PR gate, checks linked work, current head SHA, CI, review decision, review threads, merge state, and human merge authorization without merging.
| name | specrail-install |
| description | Use when installing, updating, verifying, or adopting SpecRail for agents. Guides local Codex skill installation, global AGENTS.md guidance setup, repository adoption planning, dry-run-first verification, and explicit human authorization boundaries. |
Use this skill for agent-facing SpecRail setup. The skill is the entrypoint; CLI tools are deterministic helpers the agent runs after selecting the setup route.
doctor: inspect current setup without writing files.install_local_skills: install or update local Codex skills.install_global_guidance: add or update global agent guidance.adopt_repo: plan or perform SpecRail pack adoption in a target repository.doctor.AGENT_USAGE.md.python3 tools/install_codex_skills.py --repo .
python3 checks/check_workflow.py --repo .
install_local_skills, use --apply only when the user explicitly asks
to install or update local Codex skills:python3 tools/install_codex_skills.py --repo . --apply
install_global_guidance, update ~/.codex/AGENTS.md only after an
explicit user request. Use a small managed SpecRail section or update the
existing SpecRail section; do not rewrite unrelated global instructions.adopt_repo, first report the target repo, files to copy, files that
would be preserved, and validation commands. Do not copy pack files into a
target repo unless the user explicitly asks.python3 checks/check_workflow.py --repo .
python3 -m pytest -q
When local skills were installed, also verify installed SKILL.md hashes match
skills-lock.json.
AGENTS.md, copy pack files into a
repo, create remote issues or PRs, add labels, approve, merge, or bypass
maintainers unless the user explicitly asks for that action.