brief-to-contract

Orchestrate tracker issues through the AFK chain from triage to attested contract.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ValescoAgency/flightplan --skill brief-to-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief-to-contract
Source: https://github.com/ValescoAgency/flightplan/tree/main/brief-to-contract
Command: npx skills add https://github.com/ValescoAgency/flightplan --skill brief-to-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a tracker issue through the full AFK chain — from triage to attested goal-contract — by sequencing the right per-stage skills and handling gates and HITL exits.

Core Features & Use Cases

  • End-to-end orchestration: coordinates /triage, /diagnose, /grill-with-docs, /draft-contract, and /attest to move an issue toward an attested contract.
  • Resume-detection and gating: determines where to start and enforces the transitions between stages based on tracker state and artefacts.
  • HITL-aware exits: safely hands control back to humans when required, preserving governance.

Quick Start

Invoke brief-to-contract on a tracker issue you want moved from inbound to attested contract, and confirm the detected starting stage before proceeding.

Frequently Asked Questions about brief-to-contract

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

FAQPage Schema
How do I automate issue triage and move tracker tickets to an attested contract?

You can automate the end-to-end workflow from issue triage to attested contract by using an orchestration skill that sequences per-stage tools and enforces governance gates based on tracker state and artefacts.

What is an AFK workflow chain for issue orchestration?

An AFK workflow chain is an orchestrated sequence that processes tracker issues through triage, diagnosis, grilling, drafting, and attestation stages, handling human-in-the-loop exits and resume-detection automatically.

How do I enforce gatekeeping and governance rules across a multi-stage issue workflow?

Gatekeeping and governance rules are enforced by an orchestration layer that checks tracker state and artefacts before allowing stage transitions, safely handing control back to humans when required.

Can I resume a stalled tracker issue workflow from where it left off?

Yes, resume-detection functionality identifies the correct starting stage based on existing tracker state and generated artefacts, allowing the orchestration workflow to continue seamlessly without repeating completed steps.

Do I need existing tracker artefacts to start an end-to-end issue orchestration?

No, you can invoke the orchestration on an inbound tracker issue, and it will detect the appropriate starting stage, coordinating triage through to contract attestation even without pre-existing artefacts.

What's the best way to handle human-in-the-loop exits during issue workflow orchestration?

The best approach is using a workflow orchestration system with HITL-aware exits that safely pause processing and hand control back to humans, preserving governance rules while maintaining tracker state for later resumption.