GitHub collection
tzachbon/smart-ralph
Imported from GitHub — is this yours?
30 skills imported from this repository.
Command Development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in c
Hook Development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreT
MCP Integration
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP,
Plugin Settings
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. Document
Plugin Structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidanc
Skill Development
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 Cod
ralph-specum
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.
ralph-specum-cancel
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.
ralph-specum-design
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.
ralph-specum-feedback
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.
ralph-specum-help
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-implement
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.
ralph-specum-index
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.
ralph-specum-refactor
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.
ralph-specum-requirements
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.
ralph-specum-research
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.
ralph-specum-start
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.
ralph-specum-status
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.
ralph-specum-switch
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-tasks
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.
ralph-specum-triage
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.
communication-style
Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.
delegation-principle
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
smart-ralph
Core Smart Ralph skill defining common arguments, execution modes, and shared behaviors across all Ralph plugins.
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.
communication-style
This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents
interview-framework
This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.
reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after im
smart-ralph
This skill should be used when the user asks about "ralph arguments", "quick mode", "commit spec", "max iterations", "ralph state file", "prototype overlay", "execution modes", "ralph loop", "coordinator behavior", "delegate to subagent", or needs guidance on Ralph plugin argumen
spec-workflow
This skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development", "run research phase", "generate requirements", "create design", "plan tasks", "implement spec", "check spec status", "triage a feature", "create an epic", "decompo
Agents (14)
constitution-architect
Expert in creating and maintaining project constitutions. Establishes governance principles, technology standards, and quality guidelines.
plan-architect
Technical architect for creating implementation plans from specifications. Designs architecture, data models, and API contracts aligned with constitution.
qa-engineer
QA engineer that runs verification commands and checks acceptance criteria for [VERIFY] tasks.
spec-analyst
Expert specification analyst for creating feature specs aligned with project constitution. Generates user stories, acceptance criteria, and scope definitions.
spec-executor
Autonomous task executor for spec-kit development. Executes a single task from tasks.md, verifies, commits, and signals completion.
task-planner
Expert task planner for breaking plans into executable tasks. Masters POC-first workflow, task sequencing, quality gates, and constitution alignment.
architect-reviewer
This agent should be used to "create technical design", "define architecture", "design components", "create design.md", "analyze trade-offs". Expert systems architect that designs scalable, maintainable systems with clear component boundaries.
product-manager
This agent should be used to "generate requirements", "write user stories", "define acceptance criteria", "create requirements.md", "gather product requirements". Expert product manager that translates user goals into structured requirements.
qa-engineer
This agent should be used to "run verification task", "check quality gate", "verify acceptance criteria", "run [VERIFY] task", "execute quality checkpoint". QA engineer that runs verification commands and outputs VERIFICATION_PASS or VERIFICATION_FAIL.
refactor-specialist
This agent should be used to "update spec files", "refactor requirements", "revise design", "modify tasks after execution", "incrementally update specifications". Expert at methodically reviewing and updating spec files section-by-section after execution.
spec-executor
This agent should be used to "execute a task", "implement task from tasks.md", "run spec task", "complete verification task". Autonomous executor that implements one task, verifies completion, commits changes, and signals TASK_COMPLETE.
spec-reviewer
This agent should be used to "review artifact", "validate spec output", "check quality", "review research output", "review requirements", "review design", "review tasks", "review execution", "review prototype evidence". Read-only reviewer that validates artifacts against type-spe
task-planner
This agent should be used to "create tasks", "break down design into tasks", "generate tasks.md", "plan implementation steps", "define quality checkpoints". Expert task planner that creates POC-first task breakdowns with verification steps.
triage-analyst
This agent should be used to "decompose a large feature", "triage a big task", "break down into multiple specs", "create epic decomposition", or needs guidance on splitting large features into dependency-aware spec graphs.
Commands (30)
-
/cancel— Cancel active execution safely and optionally remove the spec source -
/cancel— Cancel active execution loop and cleanup state source -
/design— Generate technical design from requirements source -
/feedback— Submit feedback or report an issue for Ralph Specum plugin. source -
/help— Show help for Ralph Specum plugin commands and workflow. source -
/implement— Start task execution loop source -
/implement— Start task execution loop source -
/index— Index codebase components and external resources into searchable specs source -
/new— Create new spec and start research phase source -
/prototype— Run or resume an optional prototype source -
/refactor— Update spec files methodically after execution (requirements -> design -> tasks) source -
/requirements— Generate requirements from goal and research source -
/research— Run or re-run research phase for current spec source -
/speckit.analyze— Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. source -
/speckit.checklist— Generate a custom checklist for the current feature based on user requirements. source -
/speckit.clarify— Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. source -
/speckit.constitution— Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync. source -
/speckit.implement— Execute the implementation plan by processing and executing all tasks defined in tasks.md source -
/speckit.plan— Execute the implementation planning workflow using the plan template to generate design artifacts. source -
/speckit.specify— Create or update the feature specification from a natural language feature description. source -
/speckit.tasks— Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts. source -
/speckit.taskstoissues— Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. source -
/start— Smart entry point for new features with auto ID and branch management source -
/start— Smart entry point that detects if you need a new spec or should resume existing source -
/status— Show current feature status and progress source -
/status— Show all specs and their current status source -
/switch— Switch active spec source -
/switch— Switch active feature source -
/tasks— Generate implementation tasks from design source -
/triage— Decompose a large feature into multiple dependency-aware specs (epic triage) source