ad-tdg

Coordinate outcome-based prompting workflows to generate ground-truth pairs and Test Dependency Maps.

728|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-tdg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ad-tdg
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-tdg
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-tdg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, repeatable workflow for outcome-based prompting when the canonical technique is known but the concrete implementation strategy remains uncertain. It guides teams to articulate a ground-truth pair, construct a Test Dependency Map, generate three implementation approaches, and select a single criterion to commit a verified implementation with an auditable trail.

Core Features & Use Cases

  • Ground-truth pair generation and documentation
  • Test Dependency Map (TDM) creation and verification
  • Drafting three implementation approaches with trade-offs
  • Single-criterion selection and traceable commit messages
  • Safe routing to ad-spike when the technique itself is uncertain

Quick Start

Define the ground-truth pair, generate the Test Dependency Map, draft three implementation approaches, and select a single evaluation criterion to verify the final result.

Frequently Asked Questions about ad-tdg

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

FAQPage Schema
What is outcome-based prompting for implementation-uncertain regimes?▼

Outcome-based prompting is a workflow that applies a known canonical technique to generate a ground-truth pair, a Test Dependency Map, and three candidate approaches to land a verified implementation.

How do I generate a Test Dependency Map for a known technical approach?▼

To generate a Test Dependency Map, you define a ground-truth pair and document the dependencies required for verification, ensuring a repeatable workflow for your selected implementation strategy.

When should I use a ground-truth pair workflow versus exploratory routing?▼

Use the ground-truth pair workflow when the canonical technique is known but implementation is uncertain, and route to exploratory spikes only when the underlying technique itself remains uncertain.

How do I select a single evaluation criterion for three implementation approaches?▼

To select a single evaluation criterion for three implementation approaches, draft the trade-offs of each approach and commit to one criterion to verify the final result with an auditable trail.

What is a documented verification loop in outcome-based prompting?▼

A documented verification loop enforces generating a ground-truth pair and Test Dependency Map, drafting three approaches, and applying a single-criterion selection to commit a verified implementation.

Can I use this workflow if the canonical technique is completely uncertain?▼

No, if the technique itself is uncertain, this workflow routes you to an exploratory spike instead, as it is specifically designed for technique-known but implementation-uncertain scenarios.