| 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. |
SLOPE Setup For Codex
Use this when the user wants SLOPE available from an agent harness.
Install Or Update
- Run
slope init --codex from the repository root.
- If the repo already has SLOPE, run
slope doctor --fix after init.
- Prefer one active Codex hook path:
- project-local:
.codex/hooks.json
- user-level:
~/.codex/hooks.json
- Avoid enabling both paths for the same repo unless the user explicitly wants duplicate hook firing.
Verify
- Run
slope doctor.
- Run
slope hook list.
- Run
python3 -m json.tool .codex/hooks.json for project-local hooks, or python3 -m json.tool ~/.codex/hooks.json for user-level hooks.
- Run
bash -n .codex/hooks/slope-guard.sh or bash -n ~/.codex/hooks/slope-guard.sh.
- Restart Codex and review
/hooks after hook changes.
Planning Discovery
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().
Explain
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.
