Menu
Show the full Specrew slash-command catalog and provide next-step guidance.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Perform a Specrew human-verdict boundary stop on the Claude host. Renders the FULL Rule 46 six-section human re-entry packet AND the verdict options as one Markdown message, with the AskUserQuestion picker disabled so the packet cannot collapse into the picker's short header/option fields. Invoke at EVERY human-judgment boundary stop (specify, clarify, plan, tasks, before-implement, implement, review, retro, feature-closeout, lifecycle-end). Triggers: boundary stop, verdict, approve / redirect / send back, why I stopped, human re-entry packet, gate stop.
{what this skill teaches agents}
Run Specrew's per-lens design workshop and collaborative design-analysis. Use whenever you work the design lenses for a feature: at specify/intake (the lens workshop) and at the design-analysis stop (co-design the architecture), and RE-INVOKE at the start of EACH new lens (architecture, data, ui-ux, security, integration, devops, requirements/NFR, observability, component). Triggers: design, design lens, lens workshop, design-analysis, architecture, trade-offs, co-design, explore options, decompose, or moving from one lens to the next. Tells you to facilitate each lens as a discussion, surface diagrams the human can actually SEE (console ASCII inline; mermaid/html to a file with a clickable file:/// link), co-design components/responsibilities/flows WITH the human instead of handing over finished options, capture the agreements, and which per-lens md to load.
| name | specrew-help |
| description | Show the full Specrew slash-command catalog and provide next-step guidance. |
Type: Discovery Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-help
Show the full Specrew slash-command catalog and provide next-step guidance. This is the canonical fallback catalog for every supported environment — reliable even when host-native /specrew- discovery is unavailable or incomplete.
/specrew-help or asks: "What Specrew commands are available?", "How do I use Specrew?", "Show me Specrew help"./specrew- suggestions are degraded or unknown.This skill provides discovery and help information only. It does not authorize or imply approval to advance any lifecycle boundary. It must never replace or absorb /speckit.* lifecycle help.
/specrew-help
No arguments are accepted in v1. The command always shows the full catalog.
Backed by: built-in catalog help output in scripts/specrew.ps1 (help mode)
The full v1 /specrew-* slash-command catalog:
| Command | Description | Notes |
|---|---|---|
/specrew-where | Show the current Specrew project status dashboard | |
/specrew-status | Alias for /specrew-where | Produces identical output |
/specrew-update | Refresh Specrew-managed assets and supported platform baselines | |
/specrew-team | Manage Squad team members and baseline-role composition | |
/specrew-review | Trigger or inspect the review-oriented workflow | |
/specrew-help | Show this catalog | |
/specrew-version | Show the installed Specrew version and slash-command compatibility state |
Next-step guidance:
/specrew-where to see your project status.specrew init from the terminal./speckit.help (separate namespace).| Failure mode | Behavior |
|---|---|
| Unsupported argument passed | Rejected; this command takes no arguments in v1 |
Part of the /specrew-* command surface. The Specrew catalog help must never absorb or shadow /speckit.* lifecycle commands. Both namespaces remain independently discoverable.
/specrew-where — project status dashboard/specrew-version — version and compatibility state