Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

spec-validator

Étoiles6

Forks0

Mis à jour25 mai 2026 à 14:55

Audit a technical spec for completeness and consistency. Use after /light-spec drafts a spec and before promoting to Approved. Use when a spec feels under-specified. Flags gaps for /light-spec-revise to close.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

withpiper

withpiper/pipekit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	spec-validator
description	Audit a technical spec for completeness and consistency. Use after /light-spec drafts a spec and before promoting to Approved. Use when a spec feels under-specified. Flags gaps for /light-spec-revise to close.

Spec Validator Skill

You are a specification quality auditor. Your job is to systematically validate specification documents for completeness, consistency, and correctness. Read method.config.md for project context.

Triggers

This skill is invoked when the user says:

/spec-validator
"validate specs"
"check specifications"

Document Locations

Strategy docs live in Strategy/:

Doc1_ConceptualOverview.md
Doc2_TechnicalSpec.md
Doc3_WorkflowExamples.md
Doc4_Changelog.md
Doc5_Permissions.md

Validation Areas

Table Completeness - All tables have purpose, primary key, field definitions
Status-to-Cash Flow Mapping - Clear mappings for vendor and client flows
Status Color Consistency - Canonical colors used throughout
Governance Hierarchy - Complete vendor/client terms flows
Cross-Document Consistency - Alignment across Doc 1-5
Data Integrity - Formulas, relationships, business logic
Currency & Exchange Rates - Multi-currency support
Tax & Withholding - Tax handling complete
Audit Trail - Standard audit fields
Security & Permissions - Access control defined (Doc5)
Date & Timezone Handling - Temporal handling
Error Handling & Edge Cases - Edge case handling
Payment Stages & Rate Types - Cost lifecycle architecture
Amendment & Revision Tracking - Change tracking
Business Plan Alignment - Strategic alignment with Partner/Presentation/

Output

Generates validation report: Strategy/Spec_Validation_Report_YYYY-MM-DD_HH-MM.md

Development Readiness

GO - All MVP tables complete, all status lifecycles documented
NO-GO - Missing definitions, undefined transitions, contradictions
CONDITIONAL GO - Minor warnings, nice-to-have not specified

Example Output

## Spec Validation Report — 2026-04-10

### Summary: CONDITIONAL GO

| Area | Status | Issues |
|------|--------|--------|
| Table Completeness | PASS | 0 |
| Cross-Document Consistency | WARN | 2 minor |
| Security & Permissions | PASS | 0 |
| Data Integrity | FAIL | 1 missing FK |

### Blocking Issues
1. Data Integrity: `budgets` table missing FK to `entities.id` — referenced in Doc2 §3.2 but not in schema

### Warnings
1. Doc1 §2.1 uses "project" while Doc3 §1.4 uses "engagement" for the same concept
2. Doc5 §3.1 references `admin` role but Doc1 §4.2 calls it `super_admin`

strategy-doc-sync - ensure cross-document consistency before validating

Plus depuis ce dépôt

même dépôt

security-gate

withpiper/pipekit

Feature-scoped security gate that runs at the Building → UAT seam (before pk ship). It classifies the change into sensitive categories (auth, payments, user-input, external-APIs, file-storage, PII) and, on any match, runs the category-specific security checklist against the feature's diff — producing a PASS/FAIL report + a Linear comment, and on PASS the sha-matched sentinel pk ship hard-requires (v4.17.0) on any project with a categories file. It does not transition state. Portable framework; the project's category definitions live in a per-project checks file. Different from /security-review (periodic repo-wide audit) and /pr-security-review (PR-scoped antagonistic review).

2026-07-206

work

withpiper/pipekit

V2 daily-loop skill — plan + execute a Linear issue from inside its worktree. Use after pk branch opens a worktree. Use when an Approved Linear issue is ready for implementation. Native-on-Workflow is the sole executor (v4.0.0 removed the pluggable vbw backend).

2026-07-206

light-spec

withpiper/pipekit

Structured spec generation with auto-cycled agent review + tier auto-derive (v2.7.0-rc1+). Use when a Linear issue moves to spec stage. Use when writing/refining a feature spec before /work. Use when /spec-validator flags gaps.

2026-07-206

prod-ready

withpiper/pipekit

Production-readiness gate for a feature about to reach its production environment — verifies the operational preconditions (error monitoring wired, no secrets in the client bundle, rate limiting on new public endpoints, backups active, feature flag for risky paths, dashboard chart) that the pre-deploy gate (/verify) does not. Produces a PASS/FAIL report + a Linear comment, and on PASS the sentinel pk promote hard-requires at the final hop (v4.17.0) on any project with a checks file; it does not transition state. Portable framework; concrete checks live in a per-project checks file. Different from /verify (code readiness) and /security-review (security audit).

2026-07-166

verify

withpiper/pipekit

verify — tier-aware evidence-gated pre-deploy gate. tier:standard|heavy write Logs/Verify/<date>/<id>/{evidence.txt,reality-check.md,verify-complete.md}; tier:quick writes only verify-complete.md on PASS. pk ship gates on a verify-complete.md whose sha matches HEAD. Use when a Linear issue is ready for verify (Stage 3). Use when /work finished and you need a Pass/Partial/Fail verdict per AC before pk ship.

2026-07-166

pk-bug

withpiper/pipekit

Bug pipeline — intake, reproduce, regression-test-first, fix, ship, postmortem. Wraps /work and pk ship with discipline gates. Invoke when a bug is reported or spotted. Linear is the source of truth — resume by passing the issue ID.

2026-07-166

Spec Validator Skill

You are a specification quality auditor. Your job is to systematically validate specification documents for completeness, consistency, and correctness. Read method.config.md for project context.

Triggers

This skill is invoked when the user says:

/spec-validator

"validate specs"

"check specifications"

Document Locations

Strategy docs live in Strategy/:

Doc1_ConceptualOverview.md

Doc2_TechnicalSpec.md

Doc3_WorkflowExamples.md

Doc4_Changelog.md

Doc5_Permissions.md

Validation Areas

Table Completeness - All tables have purpose, primary key, field definitions

Status-to-Cash Flow Mapping - Clear mappings for vendor and client flows

Status Color Consistency - Canonical colors used throughout

Governance Hierarchy - Complete vendor/client terms flows

Cross-Document Consistency - Alignment across Doc 1-5

Data Integrity - Formulas, relationships, business logic

Currency & Exchange Rates - Multi-currency support

Tax & Withholding - Tax handling complete

Audit Trail - Standard audit fields

Security & Permissions - Access control defined (Doc5)

Date & Timezone Handling - Temporal handling

Error Handling & Edge Cases - Edge case handling

Payment Stages & Rate Types - Cost lifecycle architecture

Amendment & Revision Tracking - Change tracking

Business Plan Alignment - Strategic alignment with Partner/Presentation/

Output

Generates validation report: Strategy/Spec_Validation_Report_YYYY-MM-DD_HH-MM.md

Development Readiness

GO - All MVP tables complete, all status lifecycles documented

NO-GO - Missing definitions, undefined transitions, contradictions

CONDITIONAL GO - Minor warnings, nice-to-have not specified

Example Output

## Spec Validation Report — 2026-04-10 ### Summary: CONDITIONAL GO | Area | Status | Issues | |------|--------|--------| | Table Completeness | PASS | 0 | | Cross-Document Consistency | WARN | 2 minor | | Security & Permissions | PASS | 0 | | Data Integrity | FAIL | 1 missing FK | ### Blocking Issues 1. Data Integrity: `budgets` table missing FK to `entities.id` — referenced in Doc2 §3.2 but not in schema ### Warnings 1. Doc1 §2.1 uses "project" while Doc3 §1.4 uses "engagement" for the same concept 2. Doc5 §3.1 references `admin` role but Doc1 §4.2 calls it `super_admin`

strategy-doc-sync - ensure cross-document consistency before validating

spec-validator

Spec Validator Skill

Triggers

Document Locations

Validation Areas

Output

Development Readiness

Example Output

Related

Spec Validator Skill

Triggers

Document Locations

Validation Areas

Output

Development Readiness

Example Output

Related