pharaoh-req-draft

Generate a YAML-frontmatter requirement directive with a unique ID and parent link.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting a single, well-formed requirement directive from a feature description to ensure consistent traceability and artefact linkage across projects.

Core Features & Use Cases

  • Draft a single requirement directive with a direct parent linkage.
  • Enforce artefact-catalog compliance and generate a unique ID.
  • Use case: Given a feature description, generate a single requirement block.

Quick Start

Run the pharaoh-req-draft skill with a feature description and a parent artefact to generate a single draft directive.

Frequently Asked Questions about pharaoh-req-draft

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

FAQPage Schema
How do I draft a single requirement from a feature description for traceability?

Drafting a single requirement from a feature description involves generating a YAML-frontmatter compliant requirement directive with a unique ID and a satisfies link to a parent artefact. This ensures consistent traceability across projects without decomposing the feature into multiple levels.

What is a YAML-frontmatter requirement directive in artefact-catalog compliance?

A YAML-frontmatter requirement directive is a structured metadata block enforcing artefact-catalog compliance. It generates a unique requirement ID, sets the status to draft, and creates a satisfies link to a specified parent requirement or workflow.

How do I link a new requirement to a parent workflow without decomposition?

To link a new requirement to a parent workflow without decomposition, provide a feature description and the parent artefact. The system generates a single draft requirement directive with a satisfies link, avoiding multi-level breakdown.

Can I generate multiple requirement levels from one feature description?

Generating multiple requirement levels from one feature description is not supported. This process specifically avoids decomposition, drafting only a single requirement directive linked directly to the specified parent artefact.

Does drafting requirements with this method require an existing parent artefact?

Drafting requirements with this method requires an existing parent artefact. The system creates a satisfies link to the specified parent requirement or workflow to ensure proper traceability and artefact linkage within the catalog.

What is the best way to ensure consistent requirement traceability across projects?

The best way to ensure consistent requirement traceability across projects is drafting well-formed requirement directives. Generating unique IDs and setting status to draft while linking to parent artefacts maintains standardized traceability.