Convert vague feature prompts into structured Taskwarrior tickets.
npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill feature-ticket
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
Users often have vague feature ideas that stall in early planning. This skill converts those ideas into concrete, actionable tickets for Taskwarrior.
Describe a feature idea, and I will generate a detailed Taskwarrior ticket draft.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
V4-CompanyGuide structured interviews to surface ambiguities and summarize validated requirements.
gtheysManage Taskwarrior tickets with creation, updates, comments, and workflow transitions.
jinyongpOperate the Taskwarrior CLI to manage task lifecycles with safety protocols.
thesaifalitaiDefine feature specifications with EARS-format requirements and Given/When/Then acceptance criteria.
