Skip to content

tzachbon/smart-ralph / plugins/ralph-specum-codex/skills/ralph-specum-help

ralph-specum-help

Verified

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.

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.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall