spec-review
Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/WinAppVSCE repo (the WinApp VS Code extension). Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase, the VS Code extension API, the WinApp CLI, and the ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, extension UX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.
Informações da origem
- Repositório
- microsoft/WinAppVSCE
- Última atividade na origem
- 16 de outubro de 2026 às 17:54
- Idioma detectado do SKILL.md
- inglês
- Estrelas
- 18
- Forks
- 5
Opções de instalação
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Revise os arquivos de origem
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Exibindo SKILL.md
| name | spec-review |
|---|---|
| description | Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/WinAppVSCE repo (the WinApp VS Code extension). Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase, the VS Code extension API, the WinApp CLI, and the ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, extension UX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec. |