skills.rest
laionazeredo
laionazeredoCOMMUNITY
Explore all skills by this author →
GitHub

che-plan

Generates structured Jira, Linear, or ClickUp tickets from approved specifications with BDD acceptance criteria.

Updated May 12, 2026
Search Tags:#linear#jira#bdd#epic decomposition#spec planning#vertical slice#ticket generation
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-plan-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-plan
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-plan
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-plan-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved technical specification into actionable project management tickets is manual and error-prone. This Skill automates the conversion of an Approved SPEC into structured tickets in Linear, ClickUp, or Jira, enforcing vertical-slice decomposition and BDD acceptance criteria so nothing is lost between spec and execution. ## Core Features & Use Cases - Spec-to-Ticket Generation: Reads an Approved SPEC and produces either a single ticket or an Epic with sub-tasks based on scope thresholds (B_COUNT, file count, change class). - Vertical Slice Enforcement: Decomposes Epics into exactly one sub-task per vertical slice (F0 first, critical path), rejecting horizontal layer-based decomposition unless an explicit override is declared. - BDD Acceptance Criteria: Every ticket includes Given/When/Then scenarios mapped to behavior IDs from the spec, plus dependency mapping between consecutive slices. - Use Case: After approving a feature spec for a checkout flow, run this Skill to create a Linear Epic with F0 tracer sub-task first, followed by F1 and F2 slices, each with its own BDD scenarios and blocked-by links. ## Quick Start Ask the agent to run che-plan on the approved spec for the current feature and create the tickets in your Linear project board.

Frequently Asked Questions about che-plan

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

FAQPage Schema
How do I convert a specification into Jira or Linear tickets automatically?▼

Provide an Approved SPEC and run this Skill with your target tool (Linear, ClickUp, or Jira), project board, and language. It parses the spec's frontmatter and vertical slices table, then creates a single ticket or an Epic with one sub-task per slice, each containing BDD acceptance criteria.

What is vertical slice decomposition in ticket planning?▼

Vertical slice decomposition creates one sub-task per end-to-end slice (F0, F1, ... FN) where each slice touches at least two architectural layers, such as UI plus API. This Skill rejects layer-based tasks like 'Data Layer' or 'API Layer' unless an explicit horizontal override is declared in the spec.

Does this work with ClickUp and Jira as well as Linear?▼

Yes. The Skill supports Linear via MCP integration, ClickUp via its task creation API, and Jira through a browser-based agent. You choose the target tool and project board at execution time, and Epics are created parent-first so sub-tasks can be linked.

Why does ticket generation fail with a vertical slice precondition error?▼

Generation fails when the spec lacks a defined F0 tracer slice, has three or more single-layer slices, or contains layer-based keywords without an EXPLICIT_OVERRIDE_HORIZONTAL_PLAN literal in section 2. Re-run the spec skill to fix the slices table or add the override justification and re-approve.

When does it create a single ticket instead of an Epic?▼

A single ticket is created when B_COUNT is 3 or fewer, estimated files are 5 or fewer, the change class is not 'feature', or the spec defines exactly one slice (F0 only). Larger scopes produce an Epic with sub-tasks ordered F0 first on the critical path.

Related Skills

Explore More Product & Management Skills→
J03Fr0stJ03Fr0st

to-tickets

Convert project plans and specifications into structured issue tracker tickets.

Community
Intermediate
RefractSystemsRefractSystems

planning-and-task-breakdown

Break down specifications into ordered tasks with acceptance criteria and dependencies.

Official
Intermediate
wesleyegbertowesleyegberto
3

pragmatic-programmer

Apply pragmatic programming principles to improve maintainability and adaptability.

Community
Advanced
Agent-Pattern-LabsAgent-Pattern-Labs
4

notion

Manage Notion pages, databases, and blocks through the API.

Official
Intermediate