spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

28|2|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/chohra-med/expo_boilerplate --skill spec-harness-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-harness-tickets
Source: https://github.com/chohra-med/expo_boilerplate/tree/main/.claude/skills/spec-harness-tickets
Command: npx skills add https://github.com/chohra-med/expo_boilerplate --skill spec-harness-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, error-prone work of converting scattered work items (ticket tracker issues or ad-hoc project plans) into structured, verifiable specs that align with your spec-driven development pipeline, ensuring consistent, hallucination-free planning for AI coding tools.

Core Features & Use Cases

  • Ticket-to-Spec Conversion: Pull tickets directly from connected MCPs (Linear, GitHub, Jira) and convert them into standardized specs/ directory folders with clear acceptance criteria.
  • Inline Plan Support: Turn ad-hoc work plans into complete spec packages including spec.md, plan.md, and tasks.md files for immediate use in build workflows.
  • Use Case: If you have a batch of Linear issues for a new user authentication feature, this skill will automatically generate verifiable spec folders for each ticket, ready for your AI coding tools to execute.

Quick Start

Use the spec-harness-tickets skill to pull my latest Linear tickets for the onboarding feature and convert them into build-ready specs.

Frequently Asked Questions about spec-harness-tickets

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

FAQPage Schema
How do I convert Linear tickets into structured spec documents for AI coding workflows?

To convert Linear tickets into structured spec documents, pull issues directly from connected MCPs and generate standardized spec folders containing acceptance criteria, task breakdowns, and plan documentation for AI-assisted build pipelines.

What is spec-driven development and how does ticket conversion support it?

Spec-driven development relies on structured, verifiable specification documents to guide coding. Ticket conversion supports it by transforming scattered work items into standardized spec packages with clear acceptance criteria, ensuring consistent, hallucination-free planning for AI tools.

Can I generate build-ready specs from ad-hoc project plans instead of ticket tracker issues?

Yes, you can generate build-ready specs from ad-hoc project plans. The conversion process turns inline work plans into complete spec packages, including spec.md, plan.md, and tasks.md files, ready for immediate use in build workflows.

Does ticket-to-spec conversion work with Jira and GitHub issues as well as Linear?

Yes, ticket-to-spec conversion works with Jira, GitHub, and Linear. The process pulls tickets directly from these connected task trackers to automatically generate verifiable spec folders with acceptance criteria for your engineering team.

What is the best way to automate work planning for React Native bug fixes and new features?

The best way to automate work planning for React Native features is converting ad-hoc plans and bug tickets into standardized spec folders with task breakdowns and acceptance criteria, feeding directly into AI-assisted build pipelines to eliminate manual planning errors.

Why do I need acceptance criteria generated before feeding tasks to AI coding tools?

You need acceptance criteria generated before feeding tasks to AI coding tools to ensure consistent, hallucination-free planning. Verifiable spec documents provide the structured task breakdowns required for AI pipelines and verifier tools to execute builds accurately.