Ralph Specum Help

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.claude/skills/Command Development

.claude/skills/Hook Development

.claude/skills/MCP Integration

.claude/skills/Plugin Settings

.claude/skills/Plugin Structure

Audit 0.4.1 · source sha a73b124937d9 · 18 Oct 2026Report an issue or request a re-scan

• Publishertzachbon GitHub userOwner of the repository this skill is read from
• Source foldertzachbon/smart-ralph/plugins/ralph-specum-codex/skills/ralph-specum-helpThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdicta73b124937d9A new audit runs when the source changes
• Repository statusNot archivedLast push 32 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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.

---
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
---

# Ralph Specum Help

Use this to explain the Ralph Specum surface in Codex.

## Cover

- Primary skill: `$ralph-specum`
- Helper skills: `$ralph-specum-start`, `$ralph-specum-triage`, `$ralph-specum-research`, `$ralph-specum-requirements`, `$ralph-specum-design`, `$ralph-specum-tasks`, `$ralph-specum-prototype`, `$ralph-specum-implement`, `$ralph-specum-status`, `$ralph-specum-switch`, `$ralph-specum-cancel`, `$ralph-specum-index`, `$ralph-specum-refactor`, `$ralph-specum-feedback`, `$ralph-specum-help`
- Normal flow: start goal grill, approval, research, artifact approval, requirements grill, approval, design grill, approval, tasks grill, approval, implement
- Large effort flow: triage, then start each unblocked spec
- Quick mode: only exact `--quick` bypasses interview questions; exact `--interactive` clears it. Discovery, skill loads, and artifact write gates still run
- Disk contract: `./specs` or configured roots, `.current-spec`, optional `.current-epic`, per-spec markdown files, `.ralph-state.json`

## Optional Prototype Overlay

- Direct mode: invoke `$ralph-specum-prototype` from research, requirements, design, tasks, or execution. Preserve the main phase and current checkout.
- Suggested mode: research or requirements may offer `continue to prototype`, then return to the next normal phase.
- Resume mode: use `$ralph-specum-prototype --resume <id>`. One active entry resumes automatically; several are listed deterministically for selection.
- Quick mode: run exactly one agent-owned request after requirements, ask no prototype questions, take over the oldest design blocker or select the highest-risk grounded, falsifiable question when no blocker exists, own verdict and handoff decisions, and continue to design for every result.
- Cancel mode: use `$ralph-specum-prototype --cancel <id>` or safe spec cancellation. Stop at a safe boundary, publish a reviewed immutable `cancelled` record, and preserve source and partial implementation.

Store terminal records under the resolved `<basePath>/prototypes/`. Run source work in a sibling worktree or eligible scratch area without switching the current checkout or copying unapproved dirty paths. Keep source, evidence, records, and branches local. Require separate authorization for every push, PR or issue change, and other remote action. Require exact-path and local-branch confirmation before local deletion; never delete a remote branch during prototype cleanup.

## Guidance

- Recommend `$ralph-specum` as the default entrypoint.
- Recommend `$ralph-specum-triage` when the user describes a large, multi-part, or dependency-heavy effort.
- Mention helper skills when the user wants explicit phase control.
- Explain that Ralph does not self-advance by default. The user must approve the current artifact, request changes, or explicitly continue to the next step.
- Explain that safe cancel deletes execution state only after verified immutable cancellation records exist. Full spec deletion and each prototype source deletion are separate exact-target confirmations.
- Explain that `$ralph-specum-status` reports active entries, candidates, immutable finals, quarantines, blockers, return phase/task, and source disposition.
- Mention optional bootstrap assets only when the user wants repo-local guidance.

Excerpt, first 3,545 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-18
   !CAUTION B 89 / 100

   first audit · source a73b124937d9

Questions about Ralph Specum Help

• github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-c — the audited source at commit a73b124937d9 and every finding aboveObserved · 18 Oct 2026

Spotted something wrong? Report a correction · Methodology