AGENT SKILL

specrew-update

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

License 许可
MIT
所属仓库
alonf/KeyContextAI
最近更新
2026-08-28
Stars
★ 0
Forks
0

01 前言 Front Matter

name
specrew-update
description
Refresh Specrew-managed assets and supported platform baselines in the current project.

02 资源文件 1

03 SKILL.md 正文

specrew-update

Type: Operational Skill Schema: v1 Status: Active Namespace: /specrew Canonical command: /specrew-update

Purpose

Refresh Specrew-managed assets and supported platform baselines (Spec Kit, Squad) in the current project.

When to Use

  • When a contributor wants to update Specrew assets in an existing project.
  • When refreshing the slash-command surface after a new Specrew release.
  • When synchronizing Spec Kit or Squad extensions to a newer version.
  • Invoke this skill when the user says: "Update Specrew", "Refresh Specrew assets", "Update Spec Kit", "Update Squad".

Boundary Safety

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.

Coexistence Contract

This skill is additive. Refreshing Specrew assets does not remove or shadow /speckit.* command surfaces.

Invocation

/specrew-update [--project-path <path>] [--info] [--all]
                 [--specrew] [--squad] [--spec-kit] [--skip-update-check]
                 [--upstream-latest]

Backed by: specrew update / scripts/specrew-update.ps1

Inputs

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
<!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->
--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)

Outputs

  • Update report showing which assets were refreshed, skipped, or newly provisioned.
  • --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).
  • Advisory line surfaces when upstream-latest exceeds LatestSupported, explaining "Specrew has validated only through X.Y.Z" so the user does not silently adopt untested upstream versions.
  • Default upgrade target is LatestSupported. The --upstream-latest flag opts into the historical behavior (upgrade to upstream-latest), at the user's own risk.
  • Slash-command surface status after the update. <!-- specrew-self-ok: the specrew-update skill teaches updating Specrew itself - the tool's registry is a true consumer fact -->
  • Version availability notice if a newer Specrew version is available on PSGallery.

Argument Whitelist

Only the arguments listed above are accepted in v1. Unknown or unsupported arguments are rejected immediately with explicit help guidance.

Failure 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

See Also

  • /specrew-version — inspect the current version and compatibility state before updating
  • /specrew-help — catalog fallback and full command list

04 同仓库更多 Skills