Name: speckit.implement
Author: yawbtng

Prompt file imported from yawbtng/SMU_Wiki_Agent (.cursor/commands/speckit.implement.md). Fill in {{arguments}} before use. Copyright stays with the author.

User Input

{{arguments}}

You MUST consider the user input before proceeding (if not empty).

Overview

This command launches the Ralph Wiggum implementation loop to process specifications autonomously. The agent iterates until acceptance criteria and Completion Signal requirements pass.

Prerequisites

Ralph Wiggum Plugin: Must be installed in Claude Code
```
/plugin install ralph-loop@claude-plugins-official
```
At least one spec: Specs must exist in specs/ with Completion Signal sections
Context files:
- .specify/memory/constitution.md — Project principles
- AGENTS.md — Development guidelines
- docs/ralph/master-prompt.md — Master prompt (optional, can use inline)

Execution

Option A: Single Spec

If {{arguments}} specifies a single spec (e.g., "001-user-auth"):

/ralph-loop:ralph-loop "Implement the spec {{arguments}} from specs/{{arguments}}/spec.md.

Context:
- Read .specify/memory/constitution.md for project principles
- Read AGENTS.md for development guidelines

Process:
1. Read and understand the full spec
2. Implement all requirements
3. Complete ALL items in the Completion Signal section
4. Run all tests (unit, integration, browser, visual)
5. Verify no console/network errors
6. Commit and push changes
7. Deploy if required and verify
8. Iterate until all checks pass

Output <promise>DONE</promise> when ALL checks pass." --completion-promise "DONE" --max-iterations 30

Option B: All Specs (Master Loop)

If no specific spec provided, run the master loop:

/ralph-loop:ralph-loop "Work through all specifications in specs/ folder, implementing each one until its acceptance criteria pass, then move to the next.

Context:
- Read .specify/memory/constitution.md for project principles
- Read AGENTS.md for development guidelines

For each spec in numerical order:
1. Read the spec from specs/{spec-name}/spec.md
2. Implement all requirements
3. Complete ALL items in the Completion Signal section
4. Commit, push, and verify deployment
5. Update history if required
6. Move to next spec

Output <promise>ALL_DONE</promise> when all specs complete." --completion-promise "ALL_DONE" --max-iterations 100

Fallback (No Ralph Plugin)

If the Ralph Wiggum plugin is not available:

Read docs/ralph/master-prompt.md for the master prompt
Manually iterate through specs in order
For each spec, implement until Completion Signal requirements are met
Commit and push after each major milestone
Continue until all specs complete

Install speckit.implement and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

## User Input ```text {{arguments}} ``` You **MUST** consider the user input before proceeding (if not empty). ## Overview This command launches the Ralph Wiggum implementation loop to process specifications autonomously. The agent iterates until acceptance criteria and Completion Signal requirements pass. ## Prerequisites 1. **Ralph Wiggum Plugin**: Must be installed in Claude Code ``` /plugin install ralph-loop@claude-plugins-official ``` 2. **At least one spec**: Specs must exist in `specs/` with Completion Signal sections 3. **Context files**: - `.specify/memory/constitution.md` — Project principles - `AGENTS.md` — Development guidelines - `docs/ralph/master-prompt.md` — Master prompt (optional, can use inline) ## Execution ### Option A: Single Spec If `{{arguments}}` specifies a single spec (e.g., "001-user-auth"): ``` /ralph-loop:ralph-loop "Implement the spec {{arguments}} from specs/{{arguments}}/spec.md. Context: - Read .specify/memory/constitution.md for project principles - Read AGENTS.md for development guidelines Process: 1. Read and understand the full spec 2. Implement all requirements 3. Complete ALL items in the Completion Signal section 4. Run all tests (unit, integration, browser, visual) 5. Verify no console/network errors 6. Commit and push changes 7. Deploy if required and verify 8. Iterate until all checks pass Output <promise>DONE</promise> when ALL checks pass." --completion-promise "DONE" --max-iterations 30 ``` ### Option B: All Specs (Master Loop) If no specific spec provided, run the master loop: ``` /ralph-loop:ralph-loop "Work through all specifications in specs/ folder, implementing each one until its acceptance criteria pass, then move to the next. Context: - Read .specify/memory/constitution.md for project principles - Read AGENTS.md for development guidelines For each spec in numerical order: 1. Read the spec from specs/{spec-name}/spec.md 2. Implement all requirements 3. Complete ALL items in the Completion Signal section 4. Commit, push, and verify deployment 5. Update history if required 6. Move to next spec Output <promise>ALL_DONE</promise> when all specs complete." --completion-promise "ALL_DONE" --max-iterations 100 ``` ## Fallback (No Ralph Plugin) If the Ralph Wiggum plugin is not available: 1. Read `docs/ralph/master-prompt.md` for the master prompt 2. Manually iterate through specs in order 3. For each spec, implement until Completion Signal requirements are met 4. Commit and push after each major milestone 5. Continue until all specs complete

{ "prompt": "## User Input\n\n```text\n{{arguments}}\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Overview\n\nThis command launches the Ralph Wiggum implementation loop to process specifications autonomously. The agent iterates until acceptance criteria and Completion Signal requirements pass.\n\n## Prerequisites\n\n1. **Ralph Wiggum Plugin**: Must be installed in Claude Code\n ```\n /plugin install ralph-loop@claude-plugins-official\n ```\n\n2. **At least one spec**: Specs must exist in `specs/` with Completion Signal sections\n\n3. **Context files**:\n - `.specify/memory/constitution.md` — Project principles\n - `AGENTS.md` — Development guidelines\n - `docs/ralph/master-prompt.md` — Master prompt (optional, can use inline)\n\n## Execution\n\n### Option A: Single Spec\n\nIf `{{arguments}}` specifies a single spec (e.g., \"001-user-auth\"):\n\n```\n/ralph-loop:ralph-loop \"Implement the spec {{arguments}} from specs/{{arguments}}/spec.md.\n\nContext:\n- Read .specify/memory/constitution.md for project principles\n- Read AGENTS.md for development guidelines\n\nProcess:\n1. Read and understand the full spec\n2. Implement all requirements\n3. Complete ALL items in the Completion Signal section\n4. Run all tests (unit, integration, browser, visual)\n5. Verify no console/network errors\n6. Commit and push changes\n7. Deploy if required and verify\n8. Iterate until all checks pass\n\nOutput <promise>DONE</promise> when ALL checks pass.\" --completion-promise \"DONE\" --max-iterations 30\n```\n\n### Option B: All Specs (Master Loop)\n\nIf no specific spec provided, run the master loop:\n\n```\n/ralph-loop:ralph-loop \"Work through all specifications in specs/ folder, implementing each one until its acceptance criteria pass, then move to the next.\n\nContext:\n- Read .specify/memory/constitution.md for project principles\n- Read AGENTS.md for development guidelines\n\nFor each spec in numerical order:\n1. Read the spec from specs/{spec-name}/spec.md\n2. Implement all requirements\n3. Complete ALL items in the Completion Signal section\n4. Commit, push, and verify deployment\n5. Update history if required\n6. Move to next spec\n\nOutput <promise>ALL_DONE</promise> when all specs complete.\" --completion-promise \"ALL_DONE\" --max-iterations 100\n```\n\n## Fallback (No Ralph Plugin)\n\nIf the Ralph Wiggum plugin is not available:\n\n1. Read `docs/ralph/master-prompt.md` for the master prompt\n2. Manually iterate through specs in order\n3. For each spec, implement until Completion Signal requirements are met\n4. Commit and push after each major milestone\n5. Continue until all specs complete", "variables": [ "arguments" ], "notes": "Execute implementation using Ralph Wiggum iterative loops on specs", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/yawbtng/SMU_Wiki_Agent", "path": ".cursor/commands/speckit.implement.md", "ref": "7958852ac65de84668346d329596f77f97dda476", "url": "https://github.com/yawbtng/SMU_Wiki_Agent/blob/7958852ac65de84668346d329596f77f97dda476/.cursor/commands/speckit.implement.md", "key": "yawbtng/SMU_Wiki_Agent/.cursor/commands/speckit.implement.md" } } }

speckit.implement

About

User Input

Overview

Prerequisites

Execution

Option A: Single Spec

Option B: All Specs (Master Loop)

Fallback (No Ralph Plugin)

Install speckit.implement and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews