flightplan

valesco

developmentClaude Codeby ValescoAgency

Summary

Skills bundle: /triage, /diagnose, /feedback-loop, plus tracker adapters (Linear, GitHub). Drives a tracker issue from raw inbox into a state where Valesco's autonomous CLI (runway) can pick it up. Vendor-agnostic via the tracker adapter contract.

Install to Claude Code

/plugin install flightplan@valesco

Run in Claude Code. Add the marketplace first with /plugin marketplace add ValescoAgency/flightplan if you haven't already.

README.md

<a href="https://valescoagency.com"> <img src="assets/va-bowtie-logo-primary.svg" alt="Valesco Agency" width="80" /> </a>

ValescoAgency/flightplan

Claude Code skills authored by or curated for Valesco Agency to drive tracker issues from idea to a clean handoff state for runway, Valesco's autonomous coding CLI.

Install

claude plugin marketplace add ValescoAgency/flightplan
claude plugin install flightplan@valesco

For local development against a working clone:

claude plugin marketplace add /path/to/local/flightplan
claude plugin install flightplan@valesco

After install, skills are invocable as flightplan:<skill-name> (e.g.

flightplan:triage, flightplan:diagnose).

Contents

flightplan + runway. Read on session start.

PR, repo conventions, HITL fork.

  • docs/adr/ — architectural decision records.
  • skills/<skill-name>/SKILL.md — Valesco-authored skills, one

directory per skill (Claude Code plugin convention).

Consumer skills

User-invoked skills that drive issues toward the runway pickup state (label ready-for-agent). Vendor-agnostic — they read the active tracker via the adapter system below.

| Skill | Purpose | |---|---| | /triage | Funnel issues to the ready-for-agent label with sharp acceptance criteria so runway will pick them up. HITL-aware. | | /diagnose | Six-phase debugging discipline; Phase 1 builds a deterministic feedback loop. | | /feedback-loop | The 10-pattern catalog for constructing deterministic agent-runnable signals. | | /handoff | Compact the current conversation into a handoff document so another agent can continue the work. |

Tracker adapters

Modular per-vendor adapters that satisfy the tracker contract. The active adapter is selected via tracker: in .afk/config.yml (default

linear).

| Adapter | Status | Capabilities | |---|---|---| | tracker-linear | Shipped (default) | Full — customer field, project/cycle membership, team namespace, reliable active-work detection | | tracker-github | Shipped | Reduced — no customer field, best-effort active-work detection | | tracker-jira, tracker-local-md | Deferred | — |

These compose with Matt Pocock's engineering skills (/grill-with-docs, /to-prd, /to-issues,

/improve-codebase-architecture, /zoom-out, /tdd) per the workflow in docs/workflow.md. Matt's /triage is not adopted — flightplan's /triage adds runway-prep discipline (sharp acceptance criteria, HITL routing) on top of the same canonical state machine.

Related

reads issues from the tracker, runs Claude Code in @ai-hero/sandcastle, runs an adversarial sub-agent review, opens a PR.

upstream for /grill-with-docs, /to-prd, /to-issues,

/improve-codebase-architecture, /zoom-out, /tdd.

Related plugins

Browse all →