ralph-specum-index
The ralph-specum-index skill generates searchable index specifications for existing codebases by scanning project structures and creating organized specs under the `specs/.index/` directory. Use it when explicitly requested to generate or refresh index artifacts, specifying scope parameters like paths, file types, or exclusions, with support for dry-run mode to preview changes before writing files.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-index && cp -r /tmp/ralph-specum-index/plugins/ralph-specum-codex/skills/ralph-specum-index ~/.claude/skills/ralph-specum-indexSKILL.md
# Ralph Specum Index Use this to generate searchable index specs for an existing codebase. ## Contract - Index output lives under `specs/.index/` - Use stable Ralph templates for `index.md`, component specs, and external specs - Keep component and external entries deterministic and easy to diff ## Action 1. Parse the user scope such as path, types, excludes, quick mode, dry run, or force. 2. Scan the requested code areas for controllers, services, models, helpers, migrations, or comparable project structures. 3. Generate or update: - `specs/.index/index.md` - `specs/.index/components/*.md` - `specs/.index/external/*.md` 4. Keep outputs deterministic so start, research, and triage can reuse them. 5. Include external URLs, MCP endpoints, or installed skills only when the user asked for them or they are clearly relevant. 6. In dry run mode, report what would be created without writing files. ## Response Handoff - After updating the index, name the files that changed and summarize the index scope briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to research` - Treat `continue to research` as approval of the updated index artifacts.
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 command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
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 (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
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, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
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 pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
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 guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
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.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.