// This skill should be used only when the user explicitly asks to use `$ralph-specum-help`, or explicitly asks Ralph Specum in Codex for help or command guidance.
This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
This skill should be used only when the user explicitly asks to use `$ralph-specum-design`, or explicitly asks Ralph Specum in Codex to run the design phase.
This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.
This skill should be used only when the user explicitly asks to use `$ralph-specum-implement`, or explicitly asks Ralph Specum in Codex to run implementation for approved tasks, quick mode, or an explicit continue request.
This skill should be used only when the user explicitly asks to use `$ralph-specum-index`, or explicitly asks Ralph Specum in Codex to generate or refresh index artifacts.
This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after implementation learnings.
| name | ralph-specum-help |
| description | This skill should be used only when the user explicitly asks to use `$ralph-specum-help`, or explicitly asks Ralph Specum in Codex for help or command guidance. |
| metadata | {"surface":"helper","action":"help"} |
Use this to explain the Ralph Specum surface in Codex.
$ralph-specum$ralph-specum-start, $ralph-specum-triage, $ralph-specum-research, $ralph-specum-requirements, $ralph-specum-design, $ralph-specum-tasks, $ralph-specum-implement, $ralph-specum-status, $ralph-specum-switch, $ralph-specum-cancel, $ralph-specum-index, $ralph-specum-refactor, $ralph-specum-feedback, $ralph-specum-help./specs or configured roots, .current-spec, optional .current-epic, per-spec markdown files, .ralph-state.json$ralph-specum as the default entrypoint.$ralph-specum-triage when the user describes a large, multi-part, or dependency-heavy effort.