How does this skill help with project planning?

It automates the inclusion of MoSCoW prioritization and effort estimates, making it easier for teams to gauge the scope and impact of a feature during sprint planning.

Can I create technical backend tasks with this skill?

Yes, the skill supports 'Enabler Features' specifically designed for cross-cutting technical capabilities like database integration, APIs, or authentication.

What is the T-Minus-15 process template?

It is a structured methodology for defining features that includes specific metadata, effort estimates for phases (Prep, Design, Engineer, Test), and detailed user stories with benefit hypotheses.

Does it generate Gherkin-style acceptance criteria?

Absolutely. The skill follows a strict pattern for User Stories including SCENARIO, GIVEN, WHEN, and THEN statements to ensure testable requirements.

T-Minus-15 Feature Creator

Name: T-Minus-15 Feature Creator
Author: BenGWeeks

byBenGWeeks

Productivity & Workflow

Generates comprehensive product features and user stories using the structured T-Minus-15 process template.

About

This skill transforms high-level requirements into detailed, production-ready Feature documents following the T-Minus-15 methodology. It automates the creation of structured metadata, MoSCoW prioritization, effort estimation across multiple phases, and granular user stories with Gherkin-style acceptance criteria. Ideal for Product Owners and Lead Engineers, it ensures consistency in project documentation, clearly defines benefit hypotheses, and establishes concrete deliverables for both UI-centric features and technical enablers.

Key Features

Granular user story creation with Gherkin acceptance criteria
Detailed technical documentation including data sources and UI/UX requirements
MoSCoW priority and phase-based effort estimation logic
Dedicated support for both Screen-based and Enabler feature types
Automated T-Minus-15 template generation for standardized documentation
0 GitHub stars

Use Cases

Translating stakeholder requirements into structured product backlogs
Standardizing feature documentation and acceptance criteria across a development team
Generating detailed technical enabler specs for complex infrastructure work

About

Key Features

Granular user story creation with Gherkin acceptance criteria
Detailed technical documentation including data sources and UI/UX requirements
MoSCoW priority and phase-based effort estimation logic
Dedicated support for both Screen-based and Enabler feature types
Automated T-Minus-15 template generation for standardized documentation
0 GitHub stars

Use Cases

Translating stakeholder requirements into structured product backlogs
Standardizing feature documentation and acceptance criteria across a development team
Generating detailed technical enabler specs for complex infrastructure work