feature-ticket

Convert vague feature prompts into structured Taskwarrior tickets.

4|1|Updated Apr 30, 2026

Search Tags:#planning #requirements #interview #feature #ticket #taskwarrior

Ready to run

npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill feature-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-ticket
Source: https://github.com/gtheys/pi-my-rifle-ext/tree/main/skills/feature-ticket
Command: npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill feature-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users often have vague feature ideas that stall in early planning. This skill converts those ideas into concrete, actionable tickets for Taskwarrior.

Core Features & Use Cases

Guidance-driven interview: asks targeted questions to flesh out a feature.
Ticket drafting: produces a structured Taskwarrior ticket with title, goal, behavior, acceptance criteria, and scope.
Assumptions and expansion: records decisions and open questions to guide implementation.

Quick Start

Describe a feature idea, and I will generate a detailed Taskwarrior ticket draft.

Frequently Asked Questions about feature-ticket

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

FAQPage Schema

How do I turn vague feature ideas into structured Taskwarrior tickets?▼

To turn vague feature ideas into structured Taskwarrior tickets, describe your prompt like 'add login' and a guidance-driven interview fleshes it out into a ticket with a title, goal, behavior, acceptance criteria, and scope for immediate handoff.

What information should a feature ticket include for development handoff?▼

A feature ticket for development handoff should include a precise title, goal, behavior, acceptance criteria, technical notes, and boundaries to ensure the task is actionable and scope is clearly defined.

Can I use this to plan requirements for small team projects?▼

Yes, you can use this to plan requirements for small team projects and personal work by converting ideas like 'enable dark mode' into structured tickets that record assumptions and open questions for implementation.

How does an interview-driven approach help draft feature tasks?▼

An interview-driven approach helps draft feature tasks by asking targeted questions that extract details from vague prompts, producing actionable tickets that capture assumptions, open questions, and clear boundaries.

What is the best way to add scope boundaries to a refactoring task?▼

The best way to add scope boundaries to a refactoring task is to process the prompt through an interview that defines explicit boundaries and technical notes, yielding a structured ticket with strict limits.