Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/ralph-plugin:specThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Ralph Spec Guide the user through brainstorming a new spec, then write the file. 1. Check that `PRD.md` exists — if not, tell the user to run `/ralph-plugin:init` first 2. Read `PRD.md` to understand the project 3. Read `progress.txt` and `ls specs/` to understand current state 4. Invoke `superpowers:brainstorming` to explore intent, requirements, and design with the user. If superpowers is not installed, ask questions one at a time (multiple choice preferred) to cover the same ground: - What feature or behavior to build - Acceptance criteria (machine-checkable preferred) - Any...
Guide the user through brainstorming a new spec, then write the file.
PRD.md exists — if not, tell the user to run /ralph-plugin:init firstPRD.md to understand the projectprogress.txt and ls specs/ to understand current statesuperpowers:brainstorming to explore intent, requirements, and design with the user. If superpowers is not installed, ask questions one at a time (multiple choice preferred) to cover the same ground:
ls specs/specs/NNN-slug.md using the template in specs/000-spec-template.md.examplenpx claudepluginhub jwcarman/jwcarman-marketplace --plugin ralph-plugin/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/specAuthors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.
/specGenerates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.
/specStarts interactive Kiro spec-driven development for a feature description through 3 phases, generating requirements.md (EARS), design.md (Mermaid/TS), and tasks.md.
/specGenerates feature specs via step-by-step dialogue: requirements.md (EARS notation), design.md (diagrams/TS interfaces), tasks.md (tasks/best practices).
/specGenerates structured specs from minimal feature description using Kiro method: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (impl plan).