Menu
Refresh Specrew-managed assets and supported platform baselines in the current project.
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-update |
| description | Refresh Specrew-managed assets and supported platform baselines in the current project. |
Type: Operational Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-update
Refresh Specrew-managed assets and supported platform baselines (Spec Kit, Squad) in the current project.
This skill updates distribution-managed assets only. It does not authorize or imply approval to advance any lifecycle boundary. The scope of updates is bounded by the documented argument whitelist โ no undocumented expansion occurs.
This skill is additive. Refreshing Specrew assets does not remove or shadow /speckit.* command surfaces.
/specrew-update [--project-path <path>] [--info] [--all]
[--specrew] [--squad] [--spec-kit] [--skip-update-check]
[--upstream-latest]
Backed by: specrew update / scripts/specrew-update.ps1
| Input | Type | Required | Description |
|---|---|---|---|
--project-path | string | No | Target Specrew project path (defaults to current directory) |
--info | flag | No | Show version and update information without performing updates |
--all | flag | No | Update all managed components (Specrew, Spec Kit, Squad) |
--specrew | flag | No | Update Specrew-managed assets only |
--squad | flag | No | Update Squad-managed assets only |
--spec-kit | flag | No | Update Spec Kit extension only |
--skip-update-check | flag | No | Skip the PSGallery version-available check |
--upstream-latest | flag | No | Target upstream-latest versions instead of Specrew-validated max_tested (use with care; see Outputs) |
--info table shows Current / LatestSupported (the highest version Specrew has validated against) / UpstreamLatest (advisory) / Status / Source for Specrew, Spec Kit, and Squad. Four-state Status: current, update-available-supported, ahead-of-supported (current is beyond Specrew-validated max_tested), behind-supported (current is below the floor).LatestSupported. The --upstream-latest flag opts into the historical behavior (upgrade to upstream-latest), at the user's own risk.Only the arguments listed above are accepted in v1. Unknown or unsupported arguments are rejected immediately with explicit help guidance.
| Failure mode | Behavior |
|---|---|
| Unsupported argument | Rejected immediately with command-specific help guidance |
| Missing project setup | Stop with specrew init remediation |
| Outdated compatibility baseline | Stop with upgrade/remediation guidance |
/specrew-version โ inspect the current version and compatibility state before updating/specrew-help โ catalog fallback and full command list