skills.rest
eforge-build
eforge-buildOFFICIAL
Explore all skills by this author →
WebsiteGitHub

eforge-recover

Inspect failed PRD recovery verdicts and apply retry, split, or abandon actions after user confirmation.

69|4|Updated Mar 15, 2026
Search Tags:#automation#verification#recovery#queue#prd#decision-making#recover
One-click install
npx skills add https://github.com/eforge-build/eforge --skill eforge-recover
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eforge-recover
Source: https://github.com/eforge-build/eforge/tree/main/packages/pi-eforge/skills/eforge-recover
Command: npx skills add https://github.com/eforge-build/eforge --skill eforge-recover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect the recovery process for failed PRDs and act on the verdict — re-queue, split into a successor PRD, or archive the original.

Core Features & Use Cases

  • Discover failed PRDs and surface recovery verdicts from the sidecar.
  • Present the rationale and recommended action, then require explicit user confirmation before applying recovery.
  • Apply the selected action via eforge_apply_recovery, ensuring no automated decisions.

Quick Start

Review a failed PRD, confirm the recommended action, and let the system apply the recovery.

Frequently Asked Questions about eforge-recover

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

FAQPage Schema
How do I recover a failed PRD safely without losing the original data?▼

Failed PRD recovery involves inspecting the recovery verdict from a sidecar file and requiring explicit user confirmation before applying actions like retry, split, or abandon. The system never auto-applies actions, ensuring the original PRD remains safe until you manually confirm.

What actions can I take when a PRD fails during the queue process?▼

When a PRD fails during the queue process, you can apply three recovery actions: retry the original PRD, split it into a successor PRD, or abandon and archive the original. The recommended action is surfaced from the recovery sidecar for your review.

How does the recovery sidecar determine the verdict for a failed PRD?▼

The recovery sidecar provides the verdict and rationale for a failed PRD by analyzing the failure context. It surfaces a recommended action—retry, split, or abandon—which you review before the system enacts any recovery via the apply workflow.

Can I automate the PRD recovery process to apply actions without manual confirmation?▼

No, PRD recovery cannot be automated to apply actions without manual confirmation. The system enforces safety by requiring explicit user confirmation through the recovery workflow before enacting any actions on failed PRDs.

When should I split a failed PRD instead of retrying or abandoning it?▼

Splitting a failed PRD into a successor PRD is recommended when the original PRD is too complex or broad to succeed as a single unit. The recovery sidecar provides the rationale for this verdict, which you confirm before the system creates the successor.

Related Skills

Explore More Product & Management Skills→
Quratulain-shahQuratulain-shah

monitor-system

Monitor system health, recover errors, and restart failed processes with Python scripts.

Community
Advanced
cptnfrencptnfren
3

localsetup-agentic-prd-batch

Batch-process PRD specifications to implement prioritized product requirements.

Community
Advanced
becerra-albertobecerra-alberto
4

ralph

Convert Product Requirements Documents into Ralph v2 story specifications and queue files.

Community
Intermediate
METRMETR
25

view-results

List, inspect, and retrieve detailed results from Hawk AI evaluations.

Official
Intermediate