pharaoh-req-regenerate

Regenerate a single RST requirement directive from findings JSON.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill regenerates a single requirement directive after pharaoh-req-review findings indicate issues, enabling targeted remediation without re-authoring from scratch and ensuring compatibility with the original need-id and traceability links.

Core Features & Use Cases

  • Regenerates one requirement directive from a findings JSON, preserving :id: and :satisfies: fields while updating verifiability, schema, and atomicity as needed.
  • Applies strict validation against findings JSON, ensuring the need-id matches the original directive and outputs a revised directive ready for review.
  • Supports remediation workflows for change requests within a broader traceability context and can be repeated per requirement as needed.

Quick Start

Provide the original_rst and findings_json, and run pharaoh-req-regenerate to produce a revised RST directive.

Frequently Asked Questions about pharaoh-req-regenerate

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

FAQPage Schema
How do I regenerate a single RST requirement directive after a review finds issues?

To regenerate an RST requirement directive, provide the original_rst and the findings_json from pharaoh-req-review. The skill outputs a revised directive that fixes identified issues while preserving the original need-id and traceability links.

What is the best way to fix a failed requirement verification without re-authoring the entire RST file?

The best way to fix a failed requirement is targeted remediation using the review findings. This skill regenerates the specific directive, updating the :verification: and required fields while keeping the original need-id and parent :satisfies: links intact.

When do I need to regenerate a requirement directive from a findings JSON file?

You need to regenerate a requirement directive when the overall review status is 'fail' or 'needs_work' and the original_rst is available. This allows you to correct binary and subjective axes identified during the review process.

Can I remediate multiple requirement directives in a traceability workflow?

Yes, you can remediate multiple requirement directives by repeating the regeneration process for each requirement. The skill supports remediation workflows for change requests within a broader traceability context, processing one directive per run.

Does regenerating a requirement directive preserve the original need-id and parent links?

Yes, regenerating a requirement directive strictly preserves the original need-id and its parent :satisfies: links. It validates against the findings JSON to ensure the need-id matches the original directive before outputting the revised version.