ac-trace

Analyze plan-time acceptance criteria for traceability to Foundation directives.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill ac-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ac-trace
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/ac-trace
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill ac-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicitly checks plan-time acceptance criteria (AC) to ensure they are concrete, testable, and traceable to Foundation directives or contracts, preventing drift and misalignment in planning phases.

Core Features & Use Cases

  • AC extraction and traceability: maps AC lines to Foundation IDs (directives/contracts) to produce trace-ready plans.
  • Gate-2 plan evaluation: analyzes ACs for explicitness and checkability, surfacing findings for peer review.
  • SME fan-out decision: groups independent sub-tasks into separate GSD sub-plans within a wave, while keeping coupled tasks in a single plan.
  • End-to-end validation: provides a single verdict surface and end-to-end tests (b8a-e2e) to validate the gating flow.

Quick Start

Provide a PLAN body with explicit acceptance criteria linked to Foundation IDs and run gate-2 to verify traceability.

Frequently Asked Questions about ac-trace

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

FAQPage Schema
How do I verify plan-time acceptance criteria are traceable to Foundation directives?

Acceptance criteria traceability is verified by mapping each plan-time AC line to a Foundation ID built from B4/B5 directives and contracts, ensuring every item is explicit, testable, and linked. This produces a trace-ready plan and a single gate verdict surface.

What is the best way to group independent sub-tasks into separate GSD sub-plans within a wave?

Grouping independent sub-tasks into separate GSD sub-plans within a wave is determined by SME fan-out orchestration, which isolates independent tasks into distinct plans while keeping coupled tasks together to maintain execution dependencies and prevent drift.

How do I evaluate Gate-2 plans for explicitness and checkability before peer review?

Gate-2 plan evaluation analyzes extracted acceptance criteria for explicitness and checkability, surfacing detailed findings for peer review. This validates that each criterion is concrete and testable before producing the final gate verdict.

Do I need Foundation IDs from contracts before running AC trace validation?

Foundation IDs from B4/B5 directives and contracts are required before running AC trace validation. The Skill relies on this Foundation ID surface to map acceptance criteria, ensuring traceability and producing an accurate gate verdict surface.

Why does my plan-time acceptance criteria validation fail the Gate-2 check?

Gate-2 validation fails when acceptance criteria lack explicit links to Foundation IDs, are not testable, or remain untraceable to B4/B5 directives and contracts. The detailed findings surface these specific gaps for correction before peer review.

Can I run ac-trace to orchestrate SME fan-out for coupled and independent sub-tasks?

Yes, ac-trace orchestrates SME fan-out by evaluating sub-task independence. It groups independent sub-tasks into separate GSD sub-plans within a wave while keeping coupled tasks in a single plan to preserve execution dependencies.