メニュー
Set up SLOPE in a Codex-managed repository without requiring the user to know CLI details. Trigger when the user asks to install, initialize, update, or verify SLOPE for Codex.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/srbryers/slope --skill slope-setupコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Sprint lifecycle orchestration for SLOPE-managed projects. Use when starting sprints, scoring tickets, building scorecards, running reviews, or following the routine hierarchy. Use when user says "sprint", "scorecard", "pre-round", "post-hole", "briefing", "review", "hazard", or "commit discipline".
Use SLOPE from Codex to inspect, start, claim, or close a sprint in a repository with .slope state. Trigger when the user asks to set up SLOPE, register sprint work, check active sprint status, or close out sprint work.
Run SLOPE post-merge retros from Codex and persist durable learnings. Trigger after a pull request merges, when the user asks for a retro, or when sprint closeout should save lessons into memory.
| name | slope-setup |
| description | Set up SLOPE in a Codex-managed repository without requiring the user to know CLI details. Trigger when the user asks to install, initialize, update, or verify SLOPE for Codex. |
Use this when the user wants SLOPE available from an agent harness.
slope init --codex from the repository root.slope doctor --fix after init..codex/hooks.json~/.codex/hooks.jsonslope doctor.slope hook list.python3 -m json.tool .codex/hooks.json for project-local hooks, or python3 -m json.tool ~/.codex/hooks.json for user-level hooks.bash -n .codex/hooks/slope-guard.sh or bash -n ~/.codex/hooks/slope-guard.sh./hooks after hook changes.When the user asks for a roadmap interview, run slope roadmap interview or slope roadmap interview --agent. If using MCP directly, call search({ module: "init" }) to discover getInitQuestions() and submitInitAnswers().
Tell the user that the Codex plugin bundle exposes SLOPE skills and MCP metadata under a named SLOPE integration. The bundle also includes metadata-only hook definitions for future Codex plugin-hook support, but the plugin manifest intentionally does not declare hooks because current Codex plugin validation rejects that field. Active guard enforcement uses the stable Codex hooks.json shim installed by slope init --codex while Codex plugin_hooks is under development.