pharaoh-vplan-review

Audit a test case against ISO 26262-8 and vplan axes to produce findings JSON.

24|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-vplan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pharaoh-vplan-review
Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-vplan-review
Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-vplan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors and engineering teams need a focused, auditable review of a single test case against ISO 26262-8 axes plus vplan-specific axes, producing a clear, machine-readable JSON report of findings.

Core Features & Use Cases

  • Per-axis audit of a single test case with explicit scoring and actionable items.
  • Outputs a structured JSON report suitable for integration with downstream tooling and traceability workflows.
  • Validates the presence of parent body context via needs.json and ensures proper schema for the test artifact.

Quick Start

Invoke this skill with a single test case to generate a structured findings JSON.

Frequently Asked Questions about pharaoh-vplan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a single vplan test case against ISO 26262-8 requirements?

You can audit a single vplan test case against ISO 26262-8 by invoking this skill to apply per-axis scoring and output a structured JSON report with actionable findings for traceability.

What is the best way to generate machine-readable JSON findings for vplan traceability audits?

The best way to generate machine-readable JSON findings for vplan traceability is to audit a single test case against ISO 26262-8 and vplan-specific axes, producing a structured report with actionable items.

Do I need a needs.json file to perform an ISO 26262 vplan audit?

Yes, performing an ISO 26262 vplan audit requires a needs.json file to provide the parent needs body context necessary for coverage checks and test artifact schema validation.

Can I audit multiple test case scenarios at once with a single vplan audit run?

Yes, you can audit a small set of one-test-case scenarios in a single run, applying per-axis scoring to each tc__ element to produce individual structured JSON findings.

How do I validate test artifact metadata for ISO 26262-8 vplan compliance?

You validate test artifact metadata for ISO 26262-8 vplan compliance by checking the tc artefact metadata against the parent needs body via needs.json to ensure proper schema and coverage.

What limitations exist when auditing vplan test cases for ISO 26262 traceability?

A limitation of auditing vplan test cases is the strict requirement for a parent needs.json file for coverage checks, and the skill is optimized for one-off tc__ elements or small scenario sets.