feature-brief

Generate a structured Markdown feature brief with epics and tasks.

Updated Feb 14, 2026

Search Tags:#planning #architecture #epics #backlog #tasks #feature

Ready to run

npx skills add https://github.com/Suniljit/personal-toolkit --skill feature-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-brief
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/feature-brief
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill feature-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes a discussion or feature description into a structured Markdown brief that serves as a backlog-ready artifact for epics and tasks.

Core Features & Use Cases

Structure: outputs a complete feature brief with sections for overview, goals, background, architecture, user stories, and requirements.
Backlog-ready: the document is designed so engineers can derive epics and issues directly from it.
Output location: saves the document to the repository under a kebab-case folder at _features/<feature-name>/feature-brief.md, creating the directory if needed.

Quick Start

Tell me the feature title and description, and I will generate a complete feature brief saved at _features/<feature-name>/feature-brief.md.

Frequently Asked Questions about feature-brief

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

FAQPage Schema

How do I create a structured feature brief from a discussion for my product backlog?▼

Generate a structured feature brief from a feature description to produce a backlog-ready Markdown artifact. The output includes sections for overview, goals, background, architecture, user stories, and references so engineers can directly derive epics and tasks.

Can I automatically break down a large feature into epics and tasks?▼

Yes, breaking work into epics and tasks is supported for large features, feature sets, or new projects. You provide the feature title and description, and the tool synthesizes the input into structured requirements suitable for backlog planning.

Where does the generated feature brief get saved in my repository?▼

The feature brief is saved as a Markdown file at _features/<feature-name>/feature-brief.md. It automatically creates the kebab-case directory structure within your repository if the folder does not already exist.

What sections are included in a backlog-ready feature brief?▼

A backlog-ready feature brief includes sections for overview, goals, background, architecture, user stories, and references. This structure ensures engineers have the necessary context to derive actionable epics and issues directly from the document.

Do I need any specific dependencies to generate feature briefs?▼

No specific dependencies are required to generate feature briefs. You only need to provide the feature title and description, and the tool will synthesize the input into a structured Markdown document saved directly to your repository.

When should I use a feature brief instead of writing backlog issues directly?▼

Use a feature brief when planning large features, feature sets, or new projects that require synthesized context. It serves as a backlog-ready artifact providing overview, goals, and architecture so engineers can accurately derive epics and tasks.