specrew

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.

Re-load scoped Specrew methodology discipline into context on demand — the manual recovery surface for agent drift, and the engine behind the automatic refocus injections. Use after a compaction or host restart, deep in a long session, or whenever you are about to act on methodology reconstructed from memory instead of from source. Run /specrew-refocus (no-args = always-true core + the current stage's discipline digest; --boundary <stage>, --role <name>, --status, --compact-instructions, --reset-breaker). Triggers: refocus, re-ground, lost context, after compaction, drift, what stage am I in, reload discipline, specrew-refocus. Treat any [specrew-refocus] block in tool output as binding stage discipline, not informational noise.

Re-load scoped Specrew methodology discipline into context on demand — the manual recovery surface for agent drift, and the engine behind the automatic refocus injections. Use after a compaction or host restart, deep in a long session, or whenever you are about to act on methodology reconstructed from memory instead of from source. Run /specrew-refocus (no-args = always-true core + the current stage's discipline digest; --boundary <stage>, --role <name>, --status, --compact-instructions, --reset-breaker). Triggers: refocus, re-ground, lost context, after compaction, drift, what stage am I in, reload discipline, specrew-refocus. Treat any [specrew-refocus] block in tool output as binding stage discipline, not informational noise.

Show the installed Specrew version and the slash-command compatibility state.

Show the installed Specrew version and the slash-command compatibility state.

Resume an interrupted iteration by analyzing state.md plus plan.md's task table and suggesting the next safe execution step or escalation.

Manage your Specrew Crew Interaction Profile — how much Specrew asks, explains, recommends, and auto-decides during specification intake.

Analyze in-scope requirements, produce a taskable effort model, and make overcommit visible before the plan is approved.

Detect drift between the spec, plan, tasks, and implementation; record findings to drift-log.md before review concludes.

Show the full Specrew slash-command catalog and provide next-step guidance.

Show the current Specrew project status dashboard as an alias for specrew-where.

Manage Squad team members and baseline-role composition in the current Specrew project.

Verify every task in tasks.md maps to at least one FR/SC and every FR/SC has at least one task; surface gaps before implementation begins.

Refresh Specrew-managed assets and supported platform baselines in the current project.

Show the current Specrew project status dashboard for the active feature and iteration.

Analyze in-scope requirements, produce a taskable effort model, and make overcommit visible before the plan is approved.

Detect drift between the spec, plan, tasks, and implementation; record findings to drift-log.md before review concludes.

Verify every task in tasks.md maps to at least one FR/SC and every FR/SC has at least one task; surface gaps before implementation begins.

Review iteration closeout claims by confirming the proving artifacts are both contract-compliant and versioned

Protect parsed values from later -match operations by copying PowerShell $Matches groups into local variables immediately.

Refresh Specrew-managed assets and supported platform baselines in the current project.

Show the full Specrew slash-command catalog and provide next-step guidance.

Show the current Specrew project status dashboard as an alias for specrew-where.

Manage Squad team members and baseline-role composition in the current Specrew project.

Show the current Specrew project status dashboard for the active feature and iteration.

Repair PowerShell relative-path display helpers so Windows and Linux/macOS keep project-relative bootstrap paths truthful

Keep Specrew's Copilot launch flags aligned with platform-specific REPL behavior

Review release-truth and additive public-readiness governance changes without confusing tag objects, warning lanes, or closeout guidance.

Review iteration closeout claims by confirming the proving artifacts are both contract-compliant and versioned

{what this skill teaches agents}

Review execution readiness by checking the live iteration artifacts against the contract and the live governance validator result

Embed critical governance principles into multiple artifacts for durability across document updates and session boundaries

Estimate iteration effort accurately when Phase-N clarity work is complete before execution begins and scope is well-bounded

Keep reviewer-facing documentation examples aligned with actual scaffold and replay output.

Build truthful hardening-gate fixture scenarios for blocked, approved-deferral, and ready contract coverage.