feature

Generate structured GitHub Issues with user stories, acceptance criteria, and design notes.

Updated Apr 15, 2026

Search Tags:#workflow #feature #ticket #acceptance-criteria #user-story #github-issue #design-notes

Ready to run

npx skills add https://github.com/AAbdulghany/fms --skill feature-aabdulghany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/AAbdulghany/fms --skill feature-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert vague feature ideas into structured tickets that include a user story, acceptance criteria, and design notes, ensuring consistent intake and traceability.

Core Features & Use Cases

Guided questioning to capture a user story, acceptance criteria, design notes, priority, and scope.
Automated generation of a GitHub Issue body using a standardized template, ready for review.
Preview and confirm the full ticket before creation, with automatic labeling and formatting guidelines.

Quick Start

Ask the assistant to start a new feature ticket by providing a title, guiding questions for the user story, acceptance criteria, design notes, and priority, then review and confirm before creating the GitHub issue.

Frequently Asked Questions about feature

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

FAQPage Schema

How do I convert a feature idea into a structured GitHub Issue?▼

To convert a feature idea into a structured GitHub Issue, this Skill uses guided questions to capture the user story, acceptance criteria, and design notes, then generates a standardized, formatted ticket body for review.

What is the best way to write acceptance criteria for a user story ticket?▼

Writing acceptance criteria for a user story ticket is handled by guiding you through targeted questions about feature scope and priority, automatically formatting your responses into a standardized template ready for issue creation.

Can I preview a GitHub Issue body before creating the ticket?▼

Yes, you can preview the full GitHub Issue body before creation. The Skill generates the structured ticket with user stories and design notes, presenting it for your review and confirmation before applying labels and metadata.

How do I add design notes to a feature request ticket?▼

Adding design notes to a feature request ticket involves answering guided intake questions about your feature scope. The Skill programmatically collects these inputs and formats them directly into the standardized GitHub Issue body.

Does this feature ticket workflow support portfolio-based template resolution?▼

Yes, this feature ticket workflow supports portfolio-based template resolution. It applies this resolution to present a formatted issue body, ensuring consistent intake and traceability before you confirm the ticket creation.

Why use a structured format for feature requests instead of plain text?▼

Using a structured format for feature requests solves the problem of unstructured ideas by ensuring consistent intake. It generates a standardized issue body with user stories, acceptance criteria, and design notes for better project traceability.