pharaoh-vplan-draft

Draft a tc__ test-case directive with inputs, steps, and pass criterion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers create a single, focused verification test case for a given requirement or architecture element, emitting a ready-to-run tc__ directive that links back to its parent.

Core Features & Use Cases

  • Generate a self-contained test case directive (tc__) that references a parent needs item and uses a consistent ID convention.
  • Validate parent testability and ensure the resulting test plan aligns with V-model workflows.
  • Support integration with pharaoh vplan review and related drafting/regeneration chains to maintain traceability.

Quick Start

Invoke pharaoh-vplan-draft against a validated parent need to produce a one-shot test case directive.

Frequently Asked Questions about pharaoh-vplan-draft

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

FAQPage Schema
How do I draft a verification test case for a specific requirement?

You draft a verification test case by invoking the skill against a validated parent need, which generates a structured tc__ directive. This directive contains defined inputs, execution steps, and an observable pass criterion that links back to the parent requirement.

What is a tc__ directive in V-Model validation workflows?

A tc__ directive is an RST block used in Sphinx-Needs to define a single verification test case. It ensures traceability by linking test cases to parent requirements, validating testability and enforcing unique IDs for V-Model validation workflows.

Can I generate test cases for different verification levels like integration or system testing?

Yes, you can generate test cases for different verification levels. The skill respects a configured level parameter, such as unit, integration, or system, to determine the appropriate scope and boundaries for the resulting test case directive.

Does this skill validate if a requirement is testable before generating a test case?

Yes, the skill validates the parent requirement for testability before generating the test case. It checks the needs.json-backed parent reference to ensure the requirement can be properly verified by a test directive.

How do I maintain traceability between requirements and generated test cases?

You maintain traceability by using consistent ID conventions that link the generated tc__ directives back to their parent needs. The skill integrates with pharaoh vplan review and drafting chains to preserve these links throughout the verification lifecycle.

What format does the generated test case use for Sphinx-Needs?

The generated test case uses an RST block format containing the tc__ directive. This structured output includes specific fields for test inputs, execution steps, and observable pass criteria, making it directly usable in Sphinx-Needs documentation.