skills.rest
b12consulting
b12consultingOFFICIAL
Explore all skills by this author →
WebsiteGitHub

specs-tickets

Create and manage spec-driven tickets through six lifecycle phases.

2|Updated Mar 11, 2026
Search Tags:#planning#templates#documentation#spec-driven#project-management#ticketing#lifecycle-management
One-click install
npx skills add https://github.com/b12consulting/skills --skill specs-tickets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specs-tickets
Source: https://github.com/b12consulting/skills/tree/main/skills/specs-tickets
Command: npx skills add https://github.com/b12consulting/skills --skill specs-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, manage, and resume spec-driven tickets through the full lifecycle: research, specification, planning, task definition, and implementation. This ensures teams can align work with project visions and track progress using a standard, repeatable process.

Core Features & Use Cases

  • Create new tickets with a consistent frontmatter and folder structure under specs/tickets, enabling easy tracking and handoffs.
  • Resume work on existing tickets by loading the ticket's state, related documents, and decisions to continue progress.
  • Manage the six-phase lifecycle (Research, Specify, Plan, Define Tasks, Implement, Done) with validation checkpoints and status transitions to keep work aligned with specs.

Quick Start

Describe the work to be done and I will create a new ticket with a generated ID and frontmatter in specs/tickets.

Frequently Asked Questions about specs-tickets

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

FAQPage Schema
What is spec-driven ticket management for project lifecycle tracking?▼

Spec-driven ticket management structures project work from initial description to completed implementation using standardized frontmatter, versioned documents, and lifecycle validation checkpoints to ensure alignment with project specifications.

How do I create a spec-driven ticket for new features or bugs?▼

Describe the work to be done and the system generates a new ticket with a unique ID and structured frontmatter within the specs/tickets folder, ready for lifecycle phase execution and tracking.

Can I resume work on an existing spec ticket without losing context?▼

Yes, the system loads the existing ticket's state, related documents, and prior decisions to resume progress seamlessly within the spec methodology framework.

How does the spec ticket lifecycle process work from research to done?▼

The lifecycle enforces a six-phase progression: Research, Specify, Plan, Define Tasks, Implement, and Done, with validation checkpoints and status transitions keeping execution aligned with specs.

Do I need to follow a specific methodology to use spec-driven ticketing?▼

Yes, the spec methodology reference must be loaded first to enforce frontmatter structure, versioned documents, and proper lifecycle transitions across project tickets.

What are the limitations of managing tickets without a spec-driven framework?▼

Without spec-driven ticketing, teams lack consistent folder structures, versioned documentation, and validation checkpoints, making it difficult to align work with project visions and track progress through a repeatable lifecycle.

Related Skills

Explore More Product & Management Skills→
SayBGMSayBGM

moai-foundation-core

Define MoAI-ADK foundational principles including TRUST 5 and SPEC-First DDD.

Community
Advanced
idiaz01idiaz01
3

subagent-driven-development

Coordinate autonomous subagents to execute implementation plans with two-stage reviews.

Community
Advanced
roycolumbia-coderoycolumbia-code

gsd-ai-integration-phase

Generate AI-SPEC.md design contracts and orchestrate workflow tasks.

Community
Advanced
RuifengFuRuifengFu

todo-manager

Create, categorize, and track task progress in to-do lists.

Community
Basic