This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md…
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Internal Ralph Specum contract for Codex phase interviews, skill manifests, approval, and delegation gates. Phase coordinators load this skill directly; users do not invoke it as a workflow phase.
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-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-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 invokes $ralph-specum-prototype, or explicitly asks Ralph Specum in Codex to run, resume, quick-run, or cancel an optional prototype.
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.
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
This skill should be used only when the user explicitly asks to use $ralph-specum-research, or explicitly asks Ralph Specum in Codex to run the research phase.
This skill should be used only when the user explicitly asks to use $ralph-specum-start, or explicitly asks Ralph Specum in Codex to start or resume a spec.
This skill should be used only when the user explicitly asks to use $ralph-specum-status, or explicitly asks Ralph Specum in Codex for status or active spec progress.
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.
This skill should be used only when the user explicitly asks to use $ralph-specum-tasks, or explicitly asks Ralph Specum in Codex to run the tasks phase.
This skill should be used only when the user explicitly asks to use $ralph-specum-triage, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.
Use only when the user explicitly invokes $ralph-specum, requests Ralph Specum in Codex, or asks Ralph Specum to handle a named phase or optional prototype.
Spec-driven development with task-by-task execution. Research, requirements, design, tasks, autonomous implementation, and epic triage for multi-spec feature decomposition.
★not rated 559
changed 1mo agoA
tokens not measured
originalMIT
Automatic model switching for Claude Code based on prompt complexity. No API key required.
★not rated 105▲
+5 1mo agoA
tokens not measured
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: