skills.rest
BenGWeeks
BenGWeeksCOMMUNITY
Explore all skills by this author →
Website𝕏@bengweeksGitHub

create-feature

Design end-to-end features using the T-Minus-15 process template.

Updated Jan 12, 2026
Search Tags:#template#planning#feature#deliverables#product-management#user-stories
One-click install
npx skills add https://github.com/BenGWeeks/.claude --skill create-feature-bengweeks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-feature
Source: https://github.com/BenGWeeks/.claude/tree/main/skills/create-feature
Command: npx skills add https://github.com/BenGWeeks/.claude --skill create-feature-bengweeks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams design and document end-to-end features using the T-Minus-15 process template. It ensures features carry metadata, MoSCoW prioritization, effort estimates, deliverables, and a clear benefit hypothesis.

Core Features & Use Cases

  • Structured metadata for each feature (Title, Owner, Area, Iteration)
  • MoSCoW prioritization and effort estimation per phase
  • Deliverables checklist and user-story decomposition for scoping
  • Reusable templates that speed up feature intake and alignment
  • Use Case: A product owner drafts a feature to unify epics, user stories, and acceptance criteria across teams

Quick Start

Draft a complete T-Minus-15 feature by filling in metadata, deliverables, and user stories for your next feature.

Frequently Asked Questions about create-feature

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

FAQPage Schema
How do I structure end-to-end feature deliverables with user stories and effort estimates?▼

Feature intake requires defining scope, prioritizing requirements using MoSCoW, estimating effort, listing deliverables, and writing a benefit hypothesis, all structured within the T-Minus-15 template.

What is the best way to prioritize product feature deliverables and write a benefit hypothesis?▼

MoSCoW prioritization categorizes feature requirements into Must-haves, Should-haves, Could-haves, and Won't-haves to guide effort estimation and deliverables scoping in product planning.

How do I create a feature specification that includes metadata, user stories, and acceptance criteria?▼

Yes, you can unify epics, user stories, and acceptance criteria by drafting a complete feature specification that structures deliverables and user stories across teams using the T-Minus-15 template.

Does the T-Minus-15 feature template support MoSCoW prioritization and user story decomposition?▼

Reusable feature templates speed up intake by providing a standardized structure for metadata, MoSCoW prioritization, effort estimates, and user stories, ensuring consistent alignment across teams.

Related Skills

Explore More Product & Management Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
shalevaminshalevamin

sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
Likas07Likas07

sprint-prioritizer

Prioritize agile sprint features using RICE, MoSCoW, and Value vs. Effort frameworks.

Community
Advanced
BenGWeeksBenGWeeks

create-epic

Generate Epic descriptions with the T-Minus-15 process template.

Community
Advanced