| name | module-focus |
| description | Project-local slash command alias for focused module implementation. Invoke with /module-focus when the user wants Codex to focus on one repository module and autonomously plan, code, test, commit, and attempt push using the docs-first workflow. Supports explicit --subagents modes when the user asks for delegated agent work. |
| user-invocable | true |
/module-focus
Use any text after /module-focus as the focused module task. If no module or objective is provided, ask one concise question for the module and goal.
Open and follow the project skill at .codex/skills/focused-module-implementer/SKILL.md.
Pass the module name and the remaining user text into that skill as the active focus. Preserve the named module as the scope boundary unless the user explicitly changes it.
For backend module tasks, keep frontend files out of scope unless the user explicitly requests frontend work or starts a separate frontend-focused task.
If the task text is broad, ambiguous, or asks for a new feature/behavior change, let focused-module-implementer apply its autonomous design policy: choose the best low-coupling, module-owned, interface-oriented slice and proceed unless the policy says user input is required.
Subagents are disabled by default. If the command includes --subagents, --subagents=review, --subagents=worker, --subagents=parallel, or equivalent user text, let focused-module-implementer apply its Subagent-Driven Mode rules.
If that skill is missing or unreadable, stop and tell the user. Do not continue with module implementation from memory, because this command exists specifically to preserve the docs-first workflow.
