speckit-specrew-speckit-sync-specify
Persist session-state metadata after /speckit.specify
- License 许可
- MIT
- 最近更新
- 2026-08-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- speckit-specrew-speckit-sync-specify
- metadata
- { "author": "github-spec-kit", "source": "specrew-speckit:commands/speckit.specrew-speckit.sync-specify.md" }
- description
- Persist session-state metadata after /speckit.specify
- compatibility
- Requires spec-kit project structure with .specify/ directory
03 SKILL.md 正文
Sync Specify Boundary State
Workshop readiness gate (before the spec work)
The design workshop is MANDATORY — the specify boundary cannot advance without its lens records
(lens-applicability.json with per-lens human confirmation). Deterministic: a missing or unworked
workshop throws here, BEFORE the spec work begins (Feature 185):
. .\.specify\extensions\specrew-speckit\scripts\shared-governance.ps1
$workshopRecords = Test-SpecrewWorkshopRecordsPresent -ProjectRoot .
if (-not $workshopRecords.Present) {
throw ("SPECREW WORKSHOP GATE: {0} Run the specrew-design-workshop skill and work the lenses WITH the human, then retry." -f $workshopRecords.Reason)
}
Record the arrival (before the advancement gate)
After /speckit.specify writes .specify/feature.json and the active spec artifact, record the
boundary arrival FIRST. At a first boundary this sync is what mints the pending crossing and writes
.specrew/runtime/pending-verdict-stop.md — the controller truth the verdict stop renders from.
This arrival-first order prevents a stop with no artifact:
$featureJson = Get-Content -LiteralPath .\.specify\feature.json -Raw -Encoding UTF8 | ConvertFrom-Json
$featureRef = Split-Path -Leaf $featureJson.feature_directory
pwsh -File .\.specify\extensions\specrew-speckit\scripts\sync-boundary-state.ps1 -ProjectPath . -BoundaryType specify -FeatureRef $featureRef
If the sync fails, stop and report the exact file-write error before continuing. If the sync is refused because an earlier crossing is still unapproved (the ratchet), that refusal IS the stop — surface it and wait for the human; do not work around it.
Advancement gate (after the arrival is recorded)
The gate BLOCKS until the human's verdict authorizes the crossing. Blocking is correct — and it runs AFTER the arrival sync so the stop always has controller truth to render:
. .\.specify\extensions\specrew-speckit\scripts\shared-governance.ps1
$contextState = Get-SpecrewStartContextState -ProjectRoot .
$currentBoundary = if ($contextState.Context.Contains('session_state') -and $null -ne $contextState.Context['session_state'] -and -not [string]::IsNullOrWhiteSpace([string]$contextState.Context['session_state']['boundary_type'])) {
[string]$contextState.Context['session_state']['boundary_type']
}
else {
'specify'
}
$authorization = Test-SpecrewBoundaryAuthorization -ProjectRoot . -CurrentBoundary $currentBoundary -RequestedBoundary 'specify'
if (-not $authorization.Authorized) {
Write-Output (Write-SpecrewBoundaryAuthorizationDirective -CurrentBoundary $authorization.CurrentBoundary -RequestedBoundary $authorization.RequestedBoundary -DirectiveSentinel $authorization.DirectiveSentinel)
throw $authorization.Reason
}
On a gate block, .specrew/runtime/pending-verdict-stop.md is the controller truth: render the
six-section boundary packet from its Boundary to ask for, Human approval phrase, and
Marker last line exactly values, then stop for the human's verdict. Do not infer a marker from
the phase you are in.
04 同仓库更多 Skills
windows-compatibility
Cross-platform path handling and command patterns
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn
test-discipline
Update tests when changing APIs — no exceptions
squad
Squad's command catalog and interactive menu. Invoke via /squad (slash command) or natural language ("squad commands", "what can squad do", "show me squad options"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.
squad-version-check
Internals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.