speckit-specrew-speckit-before-specify
Route the specify entry through the Specrew design workshop before producing a spec
- License 许可
- MIT
- 最近更新
- 2026-08-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- speckit-specrew-speckit-before-specify
- metadata
- { "author": "github-spec-kit", "source": "specrew-speckit:commands/speckit.specrew-speckit.before-specify.md" }
- description
- Route the specify entry through the Specrew design workshop before producing a spec
- compatibility
- Requires spec-kit project structure with .specify/ directory
03 SKILL.md 正文
Run the Specrew Design Workshop Before Specifying
You are producing a feature specification on a Specrew-governed project. Specrew does NOT generate the spec from informed defaults — the spec must be lens-informed, produced WITH the human through the design workshop. Before you write any spec content, do this:
Required
- Invoke the
specrew-design-workshopskill and work the applicable design lenses WITH the human — product-domain first, then architecture-core, component-design, data-storage, integration-api, observability-resilience, devops-operations, requirements-nfr, ui-ux, and code-implementation as applicable. Work one lens at a time: present each lens, get the human's decide / delegate / skip, and record the confirmation. Never fabricate a lens agreement — the SC-026 provenance gate validates that each lens record reflects a real human answer. - Only after the workshop is complete and the lens records exist do you write
spec.md, informed by the confirmed lens decisions (lens-informed, not lens-decorated). - Then stop at the specify boundary and render the human re-entry packet for the verdict. Do not free-run into clarify.
Failure behavior
If you are about to generate the spec from informed defaults without having run the workshop with the human, STOP — that is raw Spec Kit behavior, and this project is Specrew-governed. The specrew-design-workshop skill is the Specrew specify entry; the speckit.specify generation is the spec-writer that runs only after the workshop. Invoke the workshop and work the lenses with the human first.
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.