5d-refine

Stress-test project plans through adversarial review and edge-case analysis.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/tapania/5d-skills --skill 5d-refine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 5d-refine
Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-refine
Command: npx skills add https://github.com/tapania/5d-skills --skill 5d-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to validate and refine project plans by exposing risks and gaps before committing resources.

Core Features & Use Cases

  • Structured stress testing: Performs adversarial review, edge-case probing, stakeholder simulations, and dependency audits to surface plan-level weaknesses.
  • Quadrant and time trajectory analysis: Evaluates implications across the four quadrants and the evolution of the plan to ensure robustness.
  • Plan amendment tracking: Documents changes, risks, and action items to prepare the plan for SPEC readiness.

Quick Start

Run the refine workflow on your PLAN.md to generate a Refinement Summary that can be used to inform the SPEC phase.

Frequently Asked Questions about 5d-refine

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

FAQPage Schema
What is adversarial review for project plan refinement?

Quadrant stress testing evaluates plan implications across four perspectives and time trajectories to ensure robustness, helping teams catch plan flaws and gaps during refinement activities.

How do I stress-test a project plan to catch edge cases?

To stress-test a project plan, run an adversarial review workflow on your PLAN.md that probes edge cases, audits dependencies, and documents amendments to output a structured Refinement Summary for SPEC readiness.

When do I need to perform a quadrant stress test on my plan?

You need a quadrant stress test when validating plan robustness across stakeholder perspectives and time trajectories before moving to the SPEC phase, ensuring dependency risks and edge cases are explicitly documented.

Does plan refinement require any specific dependencies or environment setup?

Plan refinement requires no external dependencies or specific environment setup, relying solely on your existing PLAN.md as input to generate a structured Refinement Summary for the SPEC phase.

What is the best way to document plan amendments during risk management?

The best way to document plan amendments is through a structured Refinement Summary that tracks changes, dependency risks, and action items surfaced during stress testing, ensuring SPEC readiness.