skills.rest
LazyIsEfficient
LazyIsEfficientOFFICIAL
Explore all skills by this author →
GitHub

team-lead

Audit Linear/Jira tickets and author ADRs and DADs with lifecycle rules.

15|3|Updated Apr 9, 2026
Search Tags:#adr#linear#jira#triage#grooming#dad#ticket-policing
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill team-lead-lazyisefficient
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-lead
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/team-lead
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill team-lead-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This skill helps engineering teams maintain ticket quality and capture formal decisions by policing tickets in Linear/Jira and by authoring ADRs and DADs linked to work items.

Core Features & Use Cases

  • Ticket quality policing: verify acceptance criteria, owner, priority, and linkages for Linear/Jira tickets.
  • ADR/DAD generation and maintenance: author, link to tickets, and lifecycle updates.
  • Governance and documentation: map decisions to MCP workflows and enable traceability across epics and incidents.

Quick Start

Provide a ticket or ADR scenario and the Skill will generate a ticket-quality review plus ADR/DAD documentation.

Frequently Asked Questions about team-lead

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

FAQPage Schema
How do I police Linear and Jira tickets during grooming to verify acceptance criteria and ownership?▼

Ticket triage and grooming audits verify that Linear and Jira tickets have clear acceptance criteria, proper ownership, defined priorities, and correct epic linkages. This ensures work items meet governance standards before development proceeds.

What is the best way to document ADRs and DADs linked to engineering tickets?▼

Authoring ADRs and DADs linked to tickets involves applying lifecycle templates and capturing formal decisions mapped to epics. This approach maintains decision traceability across engineering work items and governance reviews.

How does ticket triage work with MCP-based workflows for engineering governance?▼

Ticket triage maps decisions to MCP-based workflows to enable traceability across epics and incidents. It references governance templates and lifecycle rules to maintain documentation quality during reviews.

Can I use this approach to enforce templates and lifecycle rules for ADRs and DADs?▼

Yes, enforcing templates and lifecycle rules for ADRs and DADs is supported through references and built-in guidance. This ensures formal decisions follow consistent structure throughout their lifecycle updates.

When do I need ADR and DAD documentation for incident governance reviews?▼

ADR and DAD documentation is needed during governance reviews when mapping formal decisions to incidents and epics. It provides traceability for architectural choices and deferred decisions across the engineering workflow.

What are the limitations of automated ticket policing for Linear and Jira quality audits?▼

Automated ticket policing focuses on structural validation of acceptance criteria, owner, priority, and linkages but requires human judgment for complex contextual decisions. It enforces templates but cannot evaluate business logic or technical feasibility.

Related Skills

Explore More Software Engineering Skills→
JeffallanJeffallan
10.9k

atlassian-mcp

Automate Atlassian MCP integrations between Jira and Confluence.

Community
Advanced
abdullah1854abdullah1854
1

cron-like-skill-placeholder

Generate Markdown Architectural Decision Records with context, decision, consequences, and alternatives.

Community
Basic
claudcherejiclaudchereji

devops-engineer

Automate CI/CD pipelines, manage infrastructure with Terraform and Ansible, and orchestrate containers with Docker and Kubernetes.

Community
Advanced
raykrayk
3

create-adr

Create Architecture Decision Records with ADR-NNN naming and lifecycle statuses.

Community
Advanced