reviewing-tribal-ticket

Review drafted Tribal tickets for correctness and design document compliance.

9|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/samfolo/tribal --skill reviewing-tribal-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-tribal-ticket
Source: https://github.com/samfolo/tribal/tree/main/.claude/skills/reviewing-tribal-ticket
Command: npx skills add https://github.com/samfolo/tribal --skill reviewing-tribal-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that drafted Tribal tickets are correct, complete, and align with design documents before being published as GitHub issues, preventing errors for implementing agents.

Core Features & Use Cases

  • Adversarial Review: Acts as a critical reviewer to identify flaws in ticket specifications.
  • Design Compliance: Verifies adherence to architectural invariants and scope-specific decisions.
  • Completeness Check: Ensures all necessary elements like error paths and acceptance criteria are covered.
  • Use Case: Before a new feature ticket is finalized, this skill rigorously checks it against all relevant design documents and codebase realities to catch potential misunderstandings or omissions.

Quick Start

Use the reviewing-tribal-ticket skill to review the draft ticket located at path 'tickets/new-feature.md'.

Frequently Asked Questions about reviewing-tribal-ticket

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

FAQPage Schema
How do I validate drafted GitHub issues against design documents before publishing?

To validate drafted GitHub issues, you can review ticket drafts against design documents to verify correctness, completeness, and adherence to architectural invariants before publication. This prevents implementation errors for AI agents.

What does a ticket review check for in software engineering milestones?

A ticket review checks for milestone alignment, completeness of acceptance criteria, scope definition clarity, and precision of language against the documentation hierarchy to ensure specifications are complete.

How do I review ticket drafts for completeness and error path coverage?

You can review ticket drafts for completeness by running an adversarial review that identifies flaws, verifies architectural compliance, and ensures all necessary elements including error paths and acceptance criteria are covered.

Can I use an AI agent to check architectural invariants in feature tickets?

Yes, you can use an AI agent to check architectural invariants in feature tickets. The agent rigorously compares ticket drafts against design documents and codebase realities to catch misunderstandings or omissions.

What is the best way to ensure ticket writing specifications are met before finalizing a feature?

The best way to ensure ticket writing specifications are met is to perform a critical adversarial review that validates precision of language and compliance against the specified documentation hierarchy before finalizing a feature.