prd-hygiene

Normalize PRD-derived GitHub backlogs into native graphs with blockedBy links.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thesobercoder/skills --skill prd-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-hygiene
Source: https://github.com/thesobercoder/skills/tree/main/prd-hygiene
Command: npx skills add https://github.com/thesobercoder/skills --skill prd-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize a PRD-derived GitHub backlog into a strict native GitHub graph so Ralph can follow it deterministically. Audits every epic's acceptance criteria against its child tasks to identify coverage gaps — AC items with no task are silent black holes that no agent will ever work on. Creates missing tasks, sharpens vague task AC, and wires everything with native sub-issues and blockedBy links. Use immediately after grill-me, write-a-prd, and prd-to-issues, or whenever a repo has PRD/epic/task issues still held together by prose instead of native links. Reach for this skill when the user wants Ralph to "just follow the graph", asks to clean up backlog hygiene, wants ordering or blockers wired correctly, mentions AC coverage gaps, or says the next task should be mechanically obvious even if they do not mention "hygiene" by name.

Core Features & Use Cases

  • Identify the target kind:prd issue and classify issues as kind:prd, kind:epic, or kind:task to reflect a clean hierarchy.
  • Audit AC coverage for each epic, create missing tasks for uncovered acceptance criteria, and sharpen vague AC details so work is actionable.
  • Wire native GitHub relationships: create sub-issue links, establish blockedBy edges, and enforce deterministic sibling ordering for a single obvious next task.
  • Improve execution discipline by building a trustworthy graph that Ralph can follow end-to-end, then report the exact next task.

Quick Start

Use the prd-hygiene skill to normalize the backlog into a deterministic, execution-ready native graph and wire blockers.

Frequently Asked Questions about prd-hygiene

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

FAQPage Schema
How do I normalize a GitHub backlog into a deterministic graph for automated execution?

To normalize a GitHub backlog into a deterministic graph, you audit epic acceptance criteria coverage, create missing tasks, and wire native sub-issue links with blockedBy edges to enforce a single obvious next task.

What are AC coverage gaps in PRD epics and how do they affect backlog execution?

AC coverage gaps are acceptance criteria items within an epic that have no corresponding child task, acting as silent black holes where automated agents will never execute work unless missing tasks are created and linked natively.

How do I wire GitHub blockedBy links and sub-issues to enforce sibling task ordering?

Wire GitHub blockedBy links and sub-issues by classifying PRD, epic, and task hierarchies, then establishing native blockedBy edges between siblings to ensure deterministic execution ordering and a mechanically obvious next task.

When should I clean up PRD backlog hygiene using native GitHub graph relationships?

Clean up PRD backlog hygiene when issues are held together by prose instead of native links, or immediately after writing PRDs and generating issues, ensuring Ralph can follow the execution graph end-to-end without ambiguity.

Why does my automated agent skip acceptance criteria when processing GitHub epics?

Automated agents skip acceptance criteria when epics have AC coverage gaps lacking child tasks; normalizing the backlog creates missing tasks and wires native sub-issue links so every AC item is actionable.