brief

Generate a structured product brief from ticket details or a manual description.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/thomfilg/ai-plugin-work --skill brief-thomfilg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/thomfilg/ai-plugin-work/tree/main/plugins/work/skills/brief
Command: npx skills add https://github.com/thomfilg/ai-plugin-work --skill brief-thomfilg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill generates a structured product brief from ticket requirements or a description, helping to organize and document project requirements efficiently.

Core Features & Use Cases

  • Ticket-based Briefing: Generate a brief from a ticket ID, extracting details like title, description, and acceptance criteria.
  • Manual Description: Generate a brief from a user-provided description, organizing the information into a structured document.
  • Use Case: When you have a new feature request, use this Skill to create a brief that outlines the requirements and goals, which can then be used to develop a spec.

Quick Start

Generate a brief for the ticket 'PROJ-123' or for the feature 'Add user dashboard'.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I create a product brief from ticket requirements?

To create a product brief from ticket requirements, you provide a ticket ID to the Skill. It extracts the title, description, and acceptance criteria, organizing them into a structured document for project planning.

Can I generate a structured project brief from a manual text description?

Yes, you can generate a structured project brief from a manual description. You input your raw feature description, and the Skill organizes the information into a clear, structured document format.

Do I need access to a ticketing system to generate a briefing document?

Yes, you need access to a ticketing system if you are generating a briefing from a ticket ID. If you lack ticket access, you can manually provide a feature description to generate the brief instead.

What is the best way to organize new feature requests for spec development?

The best way to organize new feature requests for spec development is to generate a structured product brief. This outlines the requirements and goals clearly, serving as a foundational document for your spec.

What ticket details are required for requirement gathering into a product brief?

The ticket details required for requirement gathering include the ticket title, description, and acceptance criteria. The Skill extracts these specific fields to formulate the structured product brief.