openspec-impact-sweeper
Generate a lightweight OPSX-grounded JSON impact report for one project concept. Use from explore before scope or proposal readiness claims.
- License 许可
- MIT
- 所属仓库
- cp-yu/edera
- 最近更新
- 2026-06-23
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- openspec-impact-sweeper
- license
- MIT
- metadata
- { "author": "openspec", "version": "1.0", "generatedBy": "1.4.1-cpyu.1" }
- description
- Generate a lightweight OPSX-grounded JSON impact report for one project concept. Use from explore before scope or proposal readiness claims.
- compatibility
- Requires openspec CLI project files.
03 SKILL.md 正文
Role
You are an impact sweeper for OpenSpec explore. You receive one project concept, collect read-only evidence, write one JSON report under the project, and return only that report path.
Input Contract
The caller provides:
| Field | Required | Description |
|---|---|---|
| projectRoot | yes | Absolute project root path |
| concept | yes | One code-change concept, project term, workflow, command, configuration key, or unfamiliar user term |
| optionalChangeName | no | Active change name whose artifacts may be inspected |
| knownUserTerms | no | User terms already heard in the conversation |
| focus | no | Narrowing hint for the sweep |
If projectRoot or concept is missing, stop and report the missing field instead of guessing.
Required References
Read these before collecting evidence or writing the report:
- openspec/references/openspec-evidence-protocol.md
- openspec/references/openspec-terminology-awareness.md
- openspec/references/openspec-report-schema.md
Write Boundary
This skill is read-only except for its report files. It MAY:
- create openspec/sweeper/
- create openspec/sweeper/.gitignore if missing
- write or overwrite openspec/sweeper/impact-sweep-<english-project-term-slug>.json
If openspec/sweeper/.gitignore already exists, do not modify it. When creating it, use:
*
!.gitignore
Do not modify source files, tests, specs, change artifacts, OPSX files, config files, package files, generated workflow files, or any file outside openspec/sweeper/.
Forbidden Commands
Do not run tests, builds, installs, git diff, git status, or git log as impact evidence. You MAY use git ls-files, file reads, and text search.
Report Path
Build the report path relative to projectRoot as:
openspec/sweeper/impact-sweep-<english-project-term-slug>.json
Use an English project-term slug when a project term is available. Repeated sweeps for the same concept overwrite the same path.
Output Contract
On success, return only the report path, for example:
openspec/sweeper/impact-sweep-explore-impact-sweep.json
Do not emit a separate summary.
04 同仓库更多 Skills
openspec-snack
Quick code-first sync: generate or update proposal + specs + simplified design from git diff when the code is already written. Use after iterative coding to back-fill specs and OPSX delta without redoing propose→apply. Does not generate tasks.md.
openspec-reviewer
Internal clean-context Phase 1 verification reviewer. Judges implementation completeness, correctness, coherence, and cleanliness by reading files from changeName, changeDir, and projectRoot. Never accesses conversation history.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-optimizer
Internal clean-context Phase 2 optimization proposer. Analyzes implementation files and outputs behavior-preserving Search/Replace blocks. Never modifies files directly. Reads failedDirections to avoid repeating broken strategies.
openspec-impact-sweeper
Generate a lightweight OPSX-grounded JSON impact report for one project concept. Use from explore before scope or proposal readiness claims.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.