ralph-specum-requirements
The ralph-specum-requirements skill coordinates the requirements phase of the Ralph Specum product specification workflow by delegating requirements generation to a product-manager sub-agent. It resolves the active specification, incorporates prior research and progress, clears approval gates, and manages state transitions while producing user stories, acceptance criteria, and functional requirements documented in requirements.md. Use this skill only when explicitly requested by name or when Ralph Specum is instructed to run the requirements phase.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-requirements && cp -r /tmp/ralph-specum-requirements/plugins/ralph-specum-codex/skills/ralph-specum-requirements ~/.claude/skills/ralph-specum-requirementsSKILL.md
# Ralph Specum Requirements You are a **coordinator, not a product manager** -- delegate ALL work to a `product-manager` sub-agent. ## Contract - Resolve the active spec by explicit path, exact name, or `.current-spec` - Require the spec directory to exist - Merge state fields only - Keep the Ralph disk contract unchanged ## Action 1. Resolve the active spec. If none exists, stop. 2. Read `research.md` when present, `.progress.md`, and the current state. 3. Clear any prior approval gate by merging `awaitingApproval: false` before generation. 4. Use the current brainstorming interview style unless quick mode is active. 5. **Delegate** requirements generation to a `product-manager` sub-agent. Pass research context, goal, and interview results. The sub-agent writes `requirements.md`. Do NOT write requirements.md yourself. 6. Read the sub-agent's output and validate it exists. 7. Merge state with `phase: "requirements"` and `awaitingApproval: true` (or `false` when `--quick` is active). 8. Update `.progress.md` with approved research context, user decisions, blockers, next step, and any epic constraints that must carry forward. 9. If spec commits are enabled, commit only the spec artifacts. ### Stop Behavior - **Without `--quick`**: STOP HERE. Display the walkthrough summary and approval prompt. Do NOT continue to design. Wait for the user to explicitly approve and request the next phase. - **With `--quick`**: Continue directly into design. ## Output Shape The result should include user stories, acceptance criteria, functional requirements, non-functional requirements, dependencies, exclusions, and success criteria. ## Response Handoff - After writing `requirements.md`, name `requirements.md` and summarize the requirements briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to design` - Treat `continue to design` as approval of `requirements.md`.
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.