Pi-Dev × Linear Contract

What problem does it solve?

It prevents Pi-Dev-Ops from bypassing the required governance rules when reading from or writing to Linear, ensuring routing, authorization, idempotency, and auditability stay consistent across autonomous runs.

Core Features & Use Cases

• Contract-enforced Linear write path (Skill 1): Creates the Pi-Dev spec document, milestones, and sprint plan issues in the correct order while validating required inputs and updating in place by run_id.
• Contract-enforced autonomy queue (Skill 2): Retrieves only tickets that match the allowed autonomy criteria (status + pi-dev:autonomous label) and returns structured queue details for claiming.
• Continuous drift detection (Skill 3): Flags missing mandatory statuses/labels, missing custom fields, malformed routing, stale queue depth, and blocked-reason compliance issues.
• Operational health reporting (Skill 4): Produces a daily dashboard-friendly report covering queue depth, stuck work, blocked items, milestone risk, recent completions, and an executive summary.
• Safety and governance guardrails: Requires Pi-Dev Run ID, enforces the standard footer block on created issues, and defines explicit failure-mode routing (including blocked-reason label types).

Quick Start

Ask an AI agent to file a Pi-Dev analysis artifact into Linear by invoking Skill 1 through the Linear Agent wrapper, ensuring the payload includes run_id, project routing, and the required issue footer block.