What is plan-validating-quality?

A checklist and set of rules for checking whether a project plan is complete, clear, and ready to carry out.

Use it to review plan structure, BRD and PRD requirements, technical documentation, delivery checklists, pull-request boundaries, and consistency.

It helps find missing requirements, unclear technical notes, incomplete delivery steps, and contradictions before implementation begins.

plan-validating-quality — Skill for Claude Code by wahidyankf

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 wahidyankf/ose-public --skill plan-validating-quality

Clone the repo

git clone --depth 1 https://github.com/wahidyankf/ose-public

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-validating-quality/github.svg)](https://agentmods.dev/skills/wahidyankf/ose-public/plan-validating-quality)

Your own site

<a href="https://agentmods.dev/skills/wahidyankf/ose-public/plan-validating-quality"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-validating-quality/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/wahidyankf/ose-public/plan-validating-quality"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/plan-validating-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,282 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.01282
Opus 5.5	$0.00020	$0.00513
Sonnet 5.5	$0.00010	$0.00256
Haiku 4.5	$0.00005	$0.00128

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

Security

Grade A, and why

plan-validating-quality 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 2d 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.

.agents/skills/plan-validating-quality/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Validating Plan Quality

Full methodology for plan-checker: what "complete, clear, and executable" means for a project plan, across prospective structure, bootcamp-graduate readability, requirements, material alternatives/prior art, technical docs, granular delivery checklists, and 21 numbered validation rules layered on top of the base five validation-scope sections.

Reference Modules

reference/structure-and-requirements-validation.md and reference/technical-documentation-validation.md — Validation Scope 1-3: folder/file structure, BRD/PRD content placement, technical documentation and the File-Impact tree HARD RULE.
reference/delivery-checklist-validation-part1.md and reference/delivery-checklist-validation-part2.md — Validation Scope 4: the full HARD RULE summary layer for delivery checklists and the granularity standard.
reference/pr-step-authorization-check.md and reference/pr-boundary-detection-and-consistency-validation.md — the PR Step Authorization Check (with detection scripts), No PR Outside a Declared Delivery Boundary, and Validation Scope 5 (Consistency).
reference/workflow-overview.md — the Step 0-7 execution sequence (false-positive skip list, re-validation mode, codebase inspection).
reference/factual-accuracy-validation.md — Factual Accuracy Validation (Step 4b).
reference/rule8-operational-readiness-validation.md, reference/rule9-manual-behavioural-assertion-validation.md, reference/rule10-worktree-specification-validation.md, and reference/rule11-execution-grade-clarity-validation.md — rules 8-11: Operational Readiness (5b), Manual Behavioural Assertion (5c), Worktree Specification (5d), Execution-Grade Clarity (5e).
reference/rule12-anti-hallucination-scan.md, reference/rule13-harness-neutrality-scan.md, reference/rule14-executor-tag-validation.md, and reference/rule15-phase-gate-and-natural-pause-validation.md — rules 12-15: Anti-Hallucination Scan (5f), Harness-Neutrality Scan (5g), Executor-Tag Validation (5h), Phase-Gate & Natural-Pause (5i).
reference/rules16-specs-gherkin-and-regression-test.md, reference/rule17-ui-design-funnel-completeness.md, and reference/rule18-knowledge-capture-phase-presence.md — rules 16-18: Specs & Gherkin Coverage (5j) plus the Regression Test Mandate, UI-Design-Funnel Completeness (5k), Knowledge Capture Phase Presence (5l).
reference/rule19-delivery-mode-validation-part1.md and reference/rule19-delivery-mode-validation-part2.md — rule 19: Delivery Mode Validation (5m).
reference/rule20-learning-bearing-syllabus-completeness.md — rule 20: Learning-Bearing Syllabus Completeness (5n).
reference/rule21-vercel-mcp-capability-declaration.md — rule 21: Vercel MCP Capability Declaration (5o).

Read the full file on GitHub · 88 lines

Files

What ships with it

25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 88 lines · 50 tokens per session scan A 10ab1fed90d7

Subscribe to this mod's changes

plan-validating-quality is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,282 once invoked, about $0.0002 per session on Opus 5.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-10-14.

Planning TypeScript erp islamic-finance monorepo nx sharia-compliant

turborepo

Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.

vercel/turborepo · 50 tokens

nx-plugin-for-aws

Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.

awslabs/nx-plugin-for-aws · 46 tokens

frontmcp-setup

Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…

agentfront/frontmcp · 176 tokens

investigate-cloudflare

Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.

brandhaug/b2b-saas-starter · 45 tokens

add-a-lib

Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…

lonormaly/builders-stack · 81 tokens

implement

Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.

brandhaug/b2b-saas-starter · 22 tokens