One-click install
npx skills add https://github.com/nodatall/primedirective --skill plan-refine-nodatall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-refine
Source: https://github.com/nodatall/primedirective/tree/main/skills/plan-refine
Command: npx skills add https://github.com/nodatall/primedirective --skill plan-refine-nodatall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of shipping flawed planning artifacts that lead to implementation drift, missed requirements, unexpected execution blockers, and wasted engineering effort by running a bounded iterative refinement loop with dedicated challenger and reviewer subagents to surface and resolve issues before work begins.

Core Features & Use Cases

  • Bounded Iterative Refinement: Runs up to 8 rounds of structured critique on existing PRD, TDD, and tasks-plan artifacts, with a hard stop when a fresh reviewer round finds no blocker or material issues.
  • Dual Subagent Lanes: Spawns fresh challenger subagents to pressure-test for hidden assumptions, implementation drift traps, and failure paths, and fresh reviewer subagents to adjudicate findings and enforce stop rules.
  • Guardrail Preservation: Automatically preserves research-backed and Pro-backed planning decisions, and runs final carry-forward checks to ensure no critical context is lost before handoff to execution workflows.
  • Use Case: You have a complete set of planning artifacts for a new feature drafted via the $deliver workflow, and want to pressure-test them for overlooked edge cases, conflicting requirements, and sequencing issues before your team starts implementation.

Quick Start

Invoke the plan-refine skill to run a bounded iterative refinement loop over your existing PRD, TDD, and tasks-plan artifacts to catch all blocker and material issues before starting implementation.

Frequently Asked Questions about plan-refine

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

FAQPage Schema
What is pre-execution plan refinement and when do I need it for my engineering workflow?

Pre-execution plan refinement is a structured critique process for PRD, TDD, and tasks-plan artifacts. You need it when you have complete planning artifacts and want to surface hidden assumptions, conflicting requirements, and sequencing issues before implementation begins.

How do I review a PRD and tasks-plan to catch implementation drift before coding starts?

Run a bounded iterative refinement loop with dedicated challenger and reviewer subagents over your PRD and tasks-plan. This pressure-tests planning artifacts for overlooked edge cases and failure paths, automatically stopping when a fresh reviewer round finds no blocker or material issues.

Can I use automated plan critique on multiple task plan sets and preserve research-backed decisions?

Yes, automated plan critique supports configurable plan-key selection for multiple task plan sets. It automatically preserves research-backed and Pro-backed planning decisions, running final carry-forward checks to ensure no critical context is lost before handoff to execution workflows.

What's the best way to pressure-test TDD validation artifacts for hidden assumptions and failure paths?

The best way to pressure-test TDD validation artifacts is spawning fresh challenger subagents to identify hidden assumptions and failure paths, paired with reviewer subagents that adjudicate findings and enforce stop rules, running up to 8 structured critique rounds.

Does pre-execution review support configurable round limits and refinement log preservation?

Pre-execution review supports configurable round limits up to a maximum of 8 refinement rounds, with a hard stop when no issues are found. It also offers optional refinement log preservation, alongside enforced stop rules and challenge disposition tracking.

Why does my planning artifact review need challenger and reviewer subagents instead of a single review pass?

Planning artifact review needs dual subagent lanes because dedicated challengers pressure-test for implementation drift traps while dedicated reviewers adjudicate findings and enforce stop rules. This bounded iterative approach resolves issues a single review pass would miss, eliminating execution risk from flawed planning.