speclite-validate-prd

speclite-validate-prd is a skill for Claude Code from flanliulf/SpecLite. It costs 75 tokens per session (1,178 once invoked), scanned A, original, MIT.

A workflow for reviewing a product requirements document for completeness and practicality. A PRD is a written description of a product's goals, behavior, and required capabilities.

In plain words
What is it for?
Loading a PRD, checking it against defined criteria, and producing a structured validation conclusion.
Why use it?
It helps find omissions and unclear requirements before they become misunderstandings between product, design, and engineering.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Loading a PRD, checking it against defined criteria, and producing a structured validation conclusion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flanliulf/speclite/speclite-validate-prd
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add flanliulf/SpecLite --skill speclite-validate-prd
Clone the repo
git clone --depth 1 https://github.com/flanliulf/SpecLite

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for speclite-validate-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-validate-prd/github.svg)](https://agentmods.dev/skills/flanliulf/speclite/speclite-validate-prd)
Your own site
<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-validate-prd"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-validate-prd/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for speclite-validate-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-validate-prd"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-validate-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.01178
Opus 5 $0.00037 $0.00589
Sonnet 5 $0.00015 $0.00236
Haiku 4.5 $0.00007 $0.00118

Measured 7d ago against content hash ec7ad614fcc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

speclite-validate-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

assets/source/speclite/sdlc-skills/2-plan-workflows/speclite-validate-prd/SKILL.md · 50 lines

What it actually says

[技能说明] Validate PRD 是 Speclite 规划与产品设计工作流 Skill,用于在目标项目中按配置语言、输出语言和工作流步骤完成对应制品或交付动作。

源入口说明:Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"

[核心能力] - Speclite 激活解析:解析三层 customize(base→team→user)、workflow.persistent_factsworkflow.on_complete,并通过 speclite resolve config --project-root {project-root} 加载 merged runtime config。 - 源制品发现与上下文加载:按 workflow 规约读取项目制品、配置字段、历史上下文和必要数据文件,保持源流程的输入发现语义。 - 步骤化工作流执行:按 references/workflow-details.md 与拆分后的 reference/step 文件逐步执行,遵守顺序、HALT 条件、菜单等待和状态推进规则。 - 模板化输出生成:使用 assets 中的模板或示例骨架生成文档、报告、规格或交付产物,输出语言服从 document_output_language。 - 质量校验与交接:执行清单、报告、状态同步或 completion handoff,并在退出前解析和执行 workflow.on_complete。 - 迁移一致性约束:当前运行规约只依赖 Speclite runtime,不读取旧运行目录、旧配置文件或旧命令命名空间。

[约定] 裸路径相对于 {skill-root} 解析;{project-root} 是目标项目工作目录;{speclite-runtime-root}{project-root}/_speclite{skill-name} 是目录 basename。

[激活流程] 触发后先解析 workflow,执行 activation_steps_prepend,加载 persistent_facts,运行 speclite resolve config --project-root {project-root},按 communication_language 与用户沟通,并执行 activation_steps_append。配置文件缺失或关键字段为空时必须 HALT;config.toml.example 只说明字段结构,不作为 runtime fallback。

customization 必须通过 `speclite resolve customization --skill {skill-root} --project-root {project-root}` 读取 merged JSON;`workflow.on_complete` 使用 `speclite resolve customization --skill {skill-root} --project-root {project-root} --key workflow.on_complete` 解析。默认 activation 不手写 TOML merge,不使用 `--human` 作为 machine input。

[执行流程] 1. 先完整阅读 references/workflow-details.md;该文件是从源入口转换后的权威工作流规约。随后按需读取 references/workflow-details.mdreferences/data/prd-purpose.mdreferences/steps/step-v-01-discovery.mdreferences/steps/step-v-02-format-detection.mdreferences/steps/step-v-02b-parity-check.mdreferences/steps/step-v-03-density-validation.md 等 reference 文件。 2. 执行工作流前,确认 {skill-root}{project-root}{speclite-runtime-root}{skill-name} 四个路径变量均已明确。 3. 若 workflow 指向 step 文件,必须一次只读取当前 step,完整执行后再进入下一步;遇到菜单或用户确认点时 HALT 等待。 4. 生成或更新产物时,按源 workflow 的模板、清单、状态字段和输出位置要求执行,不得因为迁移而改变核心需求。 5. 收尾前运行 checklist 或质量检查,解析 workflow.on_complete,并在输出文档末尾追加本 Skill 的生成标注。

[注意事项] - 名称、目录与 YAML name 字段保持 kebab-case 一致:speclite-validate-prd。 - references/workflow-details.md 和配套 reference 文件均为有效执行规约,不是背景资料。 - 如工作流需要模板,必须从 assets/ 中读取,不得临时省略模板结构。 - 数据和结构化参考位于 data/domain-complexity.csvdata/project-types.csv。 - config.toml.example 仅作字段结构参考,不作为 runtime fallback。 - 当前运行规约不得依赖旧运行目录、旧 YAML 配置或旧命令命名空间。 - 输出文档末尾必须追加 *本文档由 speclite-validate-prd Skill 自动生成* 标注。

[生成信息] 本 Skill 由 speclite-skill-creator 自动生成。

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 50 lines · 75 tokens per session scan A ec7ad614fcc3

Subscribe to this mod's changes

speclite-validate-prd is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 1,178 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

lain

Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…

spuentesp/lain · 90 tokens

botpipe-workflow-authoring

Author, review, and improve Botpipe workflows. Use when Codex is asked to create packaged or workspace-local Botpipe workflows, convert codebases into workflows, design provider-heavy producer/verifier steps, write Botpipe prompts/contracts, inspect Botpipe traces, or apply Codex CLI/gpt-5.5 workflow patterns.

mrauter1/botpipe · 72 tokens

pre-merge

The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits…

ndisisnd/msg · 101 tokens

intake

The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…

ndisisnd/msg · 239 tokens

merge

The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…

ndisisnd/msg · 94 tokens

msg

Root menu for msg skills, plus harness modes. --init is the one-time project bootstrap — use it when the user says "initialise project", "bootstrap repo", "set up the framework", "start a new project", or asks to set up project structure in an empty repo. Other modes: --init-staging (add a staging branch), --update…

ndisisnd/msg · 162 tokens