task-creator

Name: task-creator
Availability: InStock
Author: CommunitMe

Convert vague project requests into structured Jira tickets via interviews and impact analysis.

Updated Apr 20, 2026

Search Tags:#automation #project management #impact analysis #requirements gathering #jira #ticket creation

Ready to run

npx skills add https://github.com/CommunitMe/workspace --skill task-creator-communitme

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-creator
Source: https://github.com/CommunitMe/workspace/tree/main/.claude/skills/task-creator
Command: npx skills add https://github.com/CommunitMe/workspace --skill task-creator-communitme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @anthropic-ai/claude-code, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It streamlines the process of turning ambiguous team requests into well-defined, actionable Jira tickets, reducing miscommunication and project delays.

Core Features & Use Cases

Request Clarification: Conducts structured batched interviews to gather all necessary information from non-technical stakeholders.
Impact Evaluation: Assesses cross-repo impact based on repo map and code analysis.
Ticket Generation: Creates comprehensive Jira tickets with clear acceptance criteria, open questions, and detailed scope for product, design, and engineering teams.

Quick Start

Ask the team to describe their request clearly, then provide the detailed ticket draft for approval.

Frequently Asked Questions about task-creator

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

FAQPage Schema

How do I convert vague project requests into structured Jira tickets?▼

To convert vague project requests into structured Jira tickets, you need to conduct stakeholder interviews and evaluate repository impact to generate comprehensive documentation with clear acceptance criteria. This process involves clarifying requirements through structured questions and mapping cross-repo dependencies before drafting the final ticket for cross-team review.

What is the best way to gather requirements from non-technical stakeholders for Jira?▼

Gathering requirements from non-technical stakeholders for Jira is best achieved through structured batched interviews. This approach asks targeted questions to clarify ambiguous team requests, ensuring all necessary information is collected to define actionable project scope and reduce miscommunication before ticket generation.

How does code analysis evaluate cross-repo impact for project management?▼

Code analysis evaluates cross-repo impact for project management by assessing the repository map to identify dependencies and potential risks. This impact analysis ensures that the generated Jira tickets accurately reflect the engineering scope, preventing unexpected project delays across multiple teams.

Do I need Claude Code to automate ticket creation from ambiguous requests?▼

Yes, you need Claude Code to automate ticket creation from ambiguous requests. The automation process relies on the Claude Code environment to conduct interview questions, evaluate repository impact, and generate the detailed documentation required for seamless project execution in Jira.

What should be included in a Jira ticket for cross-team engineering review?▼

A Jira ticket for cross-team engineering review should include clear acceptance criteria, open questions, and detailed project scope. Generating these comprehensive tickets involves defining specific requirements for product, design, and engineering teams to ensure seamless project execution and minimize delays.