skills.rest
anthony-chaudhary
anthony-chaudharyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-scope

Validate GitHub issues against six axes for atomic, dispatchable work units.

30|12|Updated Jun 21, 2026
Search Tags:#github#triage#workflow-automation#issue-tracking#scope-management#agent-governance
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill ticket-scope
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-scope
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/ticket-scope
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill ticket-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity and inefficiency of dispatching poorly defined tasks to agents by enforcing a strict, six-axis contract for what constitutes a single, actionable unit of work.

Core Features & Use Cases

  • Multi-Axis Validation: Automatically checks issues against structure, size, atomicity, write-scope, cohort placement, and work-class requirements.
  • Actionable Verdicts: Provides clear, standardized feedback (DISPATCHABLE, TRIAGE, DECOMPOSE, SPLIT, or ROUTE) to guide the operator in fixing scope issues before dispatch.
  • Use Case: Before starting a new sprint or dispatch wave, run this skill against your open backlog to identify which tickets are ready for execution and which require further decomposition or clarification.

Quick Start

Run the ticket-scope skill to analyze the current open backlog and generate a readiness report for all pending issues.

Frequently Asked Questions about ticket-scope

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

FAQPage Schema
How do I validate GitHub issues for AI agent readiness before dispatching work?▼

Validate GitHub issue readiness for AI agents by linting tickets against a strict six-axis contract covering structure, size, and atomicity to ensure they represent single, dispatchable units of work. This prevents agent stranding and workflow ambiguity.

What is issue atomicity and why does it matter for workflow automation?▼

Issue atomicity ensures a GitHub ticket represents a single, actionable unit of work for AI agents. Validating atomicity through scope management prevents agent stranding by enforcing strict contracts before dispatching tasks to automated workflows.

How do I check if an issue is too large or poorly scoped for an autonomous agent?▼

Check issue scope by evaluating tickets against defined axes including size, write-scope, and work-class requirements. The validation provides actionable verdicts like DECOMPOSE or SPLIT to guide operators in fixing scope issues before dispatching to agents.

Do I need the GitHub CLI to lint issue contracts and readiness?▼

Yes, you need the GitHub CLI and the native fak toolkit integrated to perform read-only linting and verification of issue contracts. These dependencies are required to evaluate tickets against the six-axis readiness framework.

What verdicts does the ticket-scope validation provide for backlog triage?▼

Ticket-scope validation provides standardized verdicts including DISPATCHABLE, TRIAGE, DECOMPOSE, SPLIT, or ROUTE. These actionable outcomes guide operators in identifying which backlog tickets are ready for execution and which require further clarification.

Related Skills

Explore More Software Engineering Skills→
projectedanxprojectedanx
1

github-issues

Manage GitHub issue lifecycles via CLI and REST API.

Community
Intermediate
Atlas-Memory-FrameworkAtlas-Memory-Framework
1

automation-decomposition

Convert implementation plans into dependency-resolved Automation Issue Manifests.

Official
Advanced
tmalcolm-0607tmalcolm-0607

council-verdict

Override Council verdicts on governance threads with mandatory rationale and consent gates.

Community
Advanced
shwilliamsonshwilliamson

github-issues

Create structured GitHub issues with acceptance criteria, dependencies, and milestones.

Community
Basic