provenance-gate

Assess cold-pickup GitHub issues for root-cause framing via three-question validation.

3|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill provenance-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provenance-gate
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/provenance-gate
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill provenance-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This gate ensures correct root-cause framing for cold pickups by validating whether an issue describes a real root cause, not just a symptom, and by preventing unfocused work from starting without proper context.

Core Features & Use Cases

  • Three-question assessment to determine root cause vs symptom, mechanism fitness, and scope accuracy for an issue.
  • Gate and marker recording to prevent repeated framing validation within the same session and to track decisions via GitHub comments or memory.
  • Safe progression by ensuring only well-framed issues proceed to execution, reducing wasted effort and misaligned changes.

Quick Start

Run provenance-gate on a cold pickup issue to perform root-cause, mechanism-fit, and scope assessment before proceeding.

Frequently Asked Questions about provenance-gate

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

FAQPage Schema
How do I validate root cause framing for GitHub issues before execution?

Root cause framing for GitHub issues is validated using a three-question assessment that checks whether an issue describes a real root cause versus a symptom, evaluates mechanism fitness, and verifies scope accuracy before execution begins. This prevents unfocused work from starting without proper context.

What is a cold pickup issue and when does it need assessment?

A cold pickup issue is an existing GitHub issue received by a user-invocable agent without a warm handoff. Cold pickup issues need assessment when an agent requires validation of root-cause framing, mechanism fit, and scope accuracy before safe progression to execution.

How do I prevent repeated issue framing validation within the same session?

Repeated issue framing validation is prevented through gate and marker recording, which records assessment outcomes and gating decisions via GitHub comments or session memory. This formal marker signals whether an issue has passed the three-question assessment.

Can I use a three-question assessment for scope accuracy on any GitHub issue?

The three-question assessment is designed for cold pickup GitHub issues handled by user-invocable agents that lack warm handoff context. It evaluates root cause versus symptom, mechanism fitness, and scope accuracy to ensure only well-framed issues proceed to execution.

What are the limitations of automated root-cause gating for issue execution?

Automated root-cause gating requires an existing GitHub issue and a user-invocable agent to trigger the three-question assessment. It does not apply to warm handoffs where context is already provided, and it relies on GitHub comments or session memory to record gating decisions.