skills.rest
lllooollpp
lllooollppCOMMUNITY
Explore all skills by this author →
GitHub

jira-intake-clarification

Clarify Jira intake conversations into requirement_spec and ticket_plan JSON drafts.

Updated Aug 23, 2026
Search Tags:#workflow#specification#requirements#jira#ticket#intake
One-click install
npx skills add https://github.com/lllooollpp/solopreneur- --skill jira-intake-clarification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-intake-clarification
Source: https://github.com/lllooollpp/solopreneur-/tree/main/solopreneur/data/skills/jira-intake-clarification
Command: npx skills add https://github.com/lllooollpp/solopreneur- --skill jira-intake-clarification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira intake conversations can be fragmented and ambiguous, hindering quick ticket creation and alignment. This skill guides users through focused clarifications to produce structured drafts ready for Jira.

Core Features & Use Cases

  • Interactive clarification to gather title, module, requirement type, description, and acceptance criteria.
  • Continuously generates two structured artifacts: requirement_spec and ticket_plan.
  • Enforces a concise questioning strategy (up to 3 targeted questions per turn) and stops when enough information is collected.

Quick Start

Start by prompting the user for the Jira issue title and core details, then guide them with up to three targeted questions per turn until a draft requirement_spec and ticket_plan are produced.

Frequently Asked Questions about jira-intake-clarification

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

FAQPage Schema
How do I turn multi-turn chat conversations into structured Jira drafts?▼

To turn multi-turn chats into structured Jira drafts, this skill clarifies fragmented intake conversations by asking targeted questions and generating clean JSON artifacts containing the requirement specification and ticket plan.

How do I clarify ambiguous Jira intake requirements before creating a ticket?▼

To clarify ambiguous Jira intake requirements, the skill guides you through focused questioning to gather the title, module, requirement type, description, and acceptance criteria before finalizing the draft.

What is the best way to collect acceptance criteria for Jira tickets from chat logs?▼

The best way to collect acceptance criteria for Jira tickets from chat logs is to use an interactive clarification process that enforces a concise questioning strategy and stops automatically once enough information is collected.

Can I use structured questioning to generate a Jira requirement specification?▼

Yes, you can use structured questioning to generate a Jira requirement specification by applying this skill to your multi-turn chat flows, which continuously produces structured draft artifacts as details are gathered.

How many questions are asked per turn when clarifying Jira ticket details?▼

When clarifying Jira ticket details, the skill enforces a strict limit of up to three targeted questions per turn to ensure focused conversations and prevent overwhelming the user during intake.

Related Skills

Explore More Product & Management Skills→
safzanpiranisafzanpirani
1

writing-shape

Shapes raw markdown notes into structured articles through iterative editing conversations.

Community
Intermediate
darellchua2darellchua2
4

jira-git-workflow

Create JIRA tickets, Git branches, and PLAN.md files.

Community
Intermediate
ivfariasivfarias
22

speckit-constitution

Create and synchronize project constitution templates across repositories.

Community
Advanced
anton-abyzovanton-abyzov
156

spec-kit-expert

Generate RFC 2119-compliant specifications with Gherkin scenarios and user stories.

Community
Basic