Skip to content

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

ralph-specum-switch

Verified

This skill should be used only when the user explicitly asks to use `$ralph-specum-switch`, or explicitly asks Ralph Specum in Codex to switch the active spec.

Ralph Specum Switch

Use this to switch the active spec.

Derive RALPH_CODEX_PLUGIN_ROOT from this loaded skill by resolving two parent directories from the SKILL.md directory. Never derive it from the project working directory.

Contract

  • Read .claude/ralph-specum.local.md when present
  • Parse specs_dirs from frontmatter to discover all spec roots
  • Treat the first specs_dirs entry as the default root
  • Default specs root is ./specs
  • .current-spec lives in the default specs root
  • Do not guess on ambiguous names

Action

  1. Resolve the requested target by full path or exact name.
  2. If no target was provided, list available specs grouped by root.
  3. If the name is ambiguous across roots, stop and require a full path.
  4. Update .current-spec:
    • bare name for the default root
    • full path for non-default roots
  5. Read the target spec state and summarize phase, progress, approval state, and present files.
  6. Report prototype dependencies without mutating them:
    • Treat a missing activePrototypes field as an empty map.
    • When state exists, run "$RALPH_CODEX_PLUGIN_ROOT/scripts/prototype_records.py" select-downstream --base-path "$BASE_PATH" --state "$BASE_PATH/.ralph-state.json" using the selected spec's resolved basePath.
    • Show each blocker from activeBlockers with prototype ID, status, blocked artifact or transition, returnPhase, and returnTaskIndex.
    • Show staleArtifacts and staleTaskIndexes from the selection result.
    • Do not reconcile, remove active entries, edit records, or change blocker data. If no overlay or stale dependency exists, preserve the existing switch output.
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