pharaoh-arch-draft

Draft a single sphinx-needs architecture element with an RST directive block.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a single sphinx-needs architecture element (component / interface / module) from one parent requirement and emits an RST directive block linking back to the parent via :satisfies:.

Core Features & Use Cases

  • One-element-at-a-time arch drafting: derive exactly one architecture element per call (module, component, or interface) from a single parent requirement.
  • Traceability and directives: outputs an RST directive block that records the relationship to the parent with a :satisfies: link and the appropriate :type:.
  • Draft-only scope: produces a draft with :status: draft that can be reviewed and refined.

Quick Start

Invoke pharaoh-arch-draft with the required inputs: parent_req_id, arch_type, and element_description to generate a single architecture element directive.

Frequently Asked Questions about pharaoh-arch-draft

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

FAQPage Schema
How do I create a sphinx-needs architecture element from a requirement?▼

To create a sphinx-needs architecture element from a requirement, you use a drafting tool that generates an RST directive block from a parent requirement ID, linking the new element back via the :satisfies: field for traceability.

How does requirements traceability work when drafting architecture elements in RST?▼

Requirements traceability during architecture drafting works by emitting an RST directive block that records the relationship to the parent requirement using the :satisfies: link, ensuring every generated module or interface element is explicitly connected to its source.

Can I generate multiple architecture components from a single requirement at once?▼

No, you cannot generate multiple components at once. The drafting process ensures one-element-per-call, producing exactly one architecture element with :status: draft from a single parent_req_id to maintain strict traceability.

What inputs do I need to draft an architecture element with an RST directive?▼

You need a valid needs.json file and a parent_req_id input to resolve IDs. You also provide arch_type and element_description to generate the draft directive with :id:, :status: draft, and :satisfies: fields.

How do I mark a drafted architecture element as a draft in sphinx-needs?▼

To mark a drafted architecture element as a draft in sphinx-needs, the generation process automatically outputs an RST directive block containing the :status: draft field alongside the :id:, :type:, and :satisfies: attributes for later review.