What it may solve
一个基于 dsh-better-sidebar 的 SDD(规范驱动开发,Spec-Driven Development)配套Plugin:在侧边栏提供一个 Spec 工作台,围绕 OpenSpec 的标准目录结构,让「先写规范 → 再实现 → 再验证」的流程一目了然、可Action。
Imported third-party catalog description; not a Registry verification conclusion.一个基于 dsh-better-sidebar 的 SDD(规范驱动开发,Spec-Driven Development)配套Plugin:在侧边栏提供一个 Spec 工作台,围绕 OpenSpec 的标准目录结构,让「先写规范 → 再实现 → 再验证」的流程一目了然、可Action。
Author: zhangkkkai · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
一个基于 dsh-better-sidebar 的 SDD(规范驱动开发,Spec-Driven Development)配套Plugin:在侧边栏提供一个 Spec 工作台,围绕 OpenSpec 的标准目录结构,让「先写规范 → 再实现 → 再验证」的流程一目了然、可Action。
Imported third-party catalog description; not a Registry verification conclusion.0 stars · — downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 0 stars, 2 commits, 0 forks, and 0 watches; latest commit 2026-08-28.
Conclusion: This plugin has no npm package source, so this item does not apply.
Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: The dependency audit did not produce a complete report.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package structure or integrity validation did not pass.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-spec-panel. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
github:zhangkkkai/dsh-spec-panelExact version not resolved