Token导航 LogoToken导航TokenDH.com
中转站排行榜
研究检索只读github未标认证来源可访问许可证需确认审计通过

specs-review（规格审查）

Agent Skill

specs-review 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

186

周安装

8

GitHub Stars

2

下载量

65
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：specs-review（规格审查）
来源仓库：https://github.com/b12consulting/skills
仓库路径：skills/specs-review
安装命令：
npx skills add https://github.com/b12consulting/skills --skill specs-review
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills
npx skills add https://github.com/b12consulting/skills --skill specs-review

简介

specs-review 用于查找、检索和筛选相关信息。

  • 适用于对技术规格或开发内容进行审查与筛选。
  • 通过 npx skills add 命令从指定仓库安装后调用。
  • 建议在使用前确认权限及是否允许联网查询外部资源。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI，接入前应确认版本、权限和运行环境要求。

SKILL.md

Specs Review

Audit the health and consistency of a project's spec-driven documentation.

Skill Dependencies

This skill is part of a set of skills designed to work together:

  • spec-driven — Methodology reference (structure, formats, rules)
  • specs-setup — Initialize specs/ for a new project
  • specs-tickets — Create and execute tickets through their lifecycle
  • specs-review (this skill) — Audit specs health and consistency

If any of these skills are missing from the project, instruct the user to install them before proceeding:

npx skills add b12consulting/skills --skill <missing_skill>

Always load the spec-driven skill first for the full methodology reference.

Procedure

1. Structural Completeness

Verify all required files exist:

  • specs/README.md
  • specs/Vision.md
  • specs/PRD.md
  • specs/Goals.md
  • specs/Architecture/README.md
  • specs/Glossary.md
  • specs/Changelog.md
  • specs/decisions/ directory
  • specs/tickets/ directory

Report any missing files. Suggest running specs-setup if critical files are absent.

2. Document Quality

For each project-level document, check:

DocumentCheck
Vision.mdHas vision statement, problem statement, and target audience?
PRD.mdHas functional requirements, non-functional requirements, and scope? Are requirements numbered (FR-1, FR-2...)?
Goals.mdHas measurable success metrics? Are milestones defined with target dates?
Architecture/README.mdHas system overview, key components, and tech stack? Links to sub-documents if they exist?
Glossary.mdHas at least a few terms? Are terms used consistently in other documents?
Changelog.mdIs up to date with recent completed tickets?
README.mdDoes the active tickets table match actual ticket statuses? Is the "last updated" date recent?

Flag documents that are empty templates (never filled in) or have placeholder content.

3. Ticket Health

Scan all ticket folders in specs/tickets/ and check each one:

Frontmatter integrity:

  • Does every ticket have a README.md with valid frontmatter (id, title, status, created, updated)?
  • Are status values valid (research, specifying, open-questions, planned, in-progress, done, archived)?

Lifecycle consistency:

  • Does a ticket marked in-progress have a Tasks.md with at least some unchecked items?
  • Does a ticket marked done have all acceptance criteria in Spec.md checked off?
  • Does a ticket marked planned have both Spec.md and Plan.md?
  • Does a ticket marked archived have a documented reason in its README.md body?

Stale tickets:

  • Any ticket with status in-progress or research whose updated date is more than 2 weeks old? Flag as potentially stale.
  • Any ticket with status open-questions that has been waiting for decisions? Flag with the pending questions.

Orphaned files:

  • Any ticket folder missing a README.md?
  • Any Decisions.md with items still in the Open section for a ticket that has moved past specifying?

Report findings as a table:

#TitleStatusIssues
001...in-progressStale (last updated 3 weeks ago)
002...doneAcceptance criteria not all checked

4. Cross-Reference Consistency

Check that documents reference each other correctly:

  • README.md dashboard vs. reality: Do the "Active Tickets" and "Recently Completed" tables match actual ticket statuses?
  • ADR references: Are ADRs referenced in the tickets that triggered them? Are ADR-modified documents (Vision, PRD, Goals, Architecture) updated accordingly?
  • Glossary usage: Scan Vision, PRD, and Architecture for domain terms. Are they defined in the Glossary? Are there Glossary terms that appear unused?
  • Architecture sub-documents: If Architecture/README.md links to sub-documents, do those files exist?

5. Drift Detection

Compare specs against the codebase:

  • Does the tech stack in Architecture/README.md match the actual dependencies (check package.json, pyproject.toml, Cargo.toml, etc.)?
  • Do the key components described in Architecture match the actual project structure?
  • Are there functional requirements in PRD.md that don't correspond to any ticket (planned or completed)?

This step requires codebase analysis. Flag potential drift but note that confirmation with the user is needed — apparent drift may be intentional and just not yet documented.

6. Report

Summarize findings in three categories:

Critical — Blocks correct agent behavior:

  • Missing ground truth documents (Vision, PRD, Architecture)
  • Tickets with invalid or missing frontmatter
  • Conflicts between specs and code that could lead to wrong implementation

Warning — Should be addressed soon:

  • Stale tickets
  • Unresolved open questions
  • README dashboard out of sync
  • Empty or placeholder documents

Suggestion — Improvements for completeness:

  • Missing Glossary terms
  • Tickets without Journal.md that had complex processes
  • Architecture that could benefit from sub-documents

7. Propose Actions

For each finding, propose a concrete action:

  • "Create ADR to document the React-to-Vue migration that happened in ticket 005"
  • "Update specs/README.md — tickets 003 and 004 are marked done but still in Active Tickets"
  • "Ticket 007 has been in-progress for 3 weeks with no updates — ask the owner for status"
  • "Add 'workspace' and 'campaign' to the Glossary — used in PRD but not defined"

Ask the user which actions to take. Execute approved actions immediately.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.52%
按下载量换算22

Claude

30.48%
按下载量换算20

Cursor

19.47%
按下载量换算13

Gemini CLI

9.74%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容，本身偏只读；真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/b12consulting/skills

SKILL.md 来源

github.com

/b12consulting/skills/tree/main/skills/specs-review

skills-sh

skills.sh

/b12consulting/skills/specs-review

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

specs-extractor（规格提取器）

specs-extractor 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

specs-tickets（规格票）

用于处理 Jira 项目、任务、缺陷、Sprint、负责人和状态流转。它适合让 Agent 辅助查询工单、汇总迭代进展、创建任务或整理需求和缺陷信息。使用时要确认项目权限、字段配置和工作流规则，不同团队的 Issue 类型、状态和必填字段可能不同；涉及批量改状态、改负责人或创建工单时，应先预览变更内容再执行。