feature▌

bdd-feature-generator

Structured requirements workshops that produce EARS-format specifications, user stories, acceptance criteria, and implementation checklists. \n \n Conducts systematic discovery interviews from both product and engineering perspectives, using structured questioning to elicit requirements before writing specifications \n Outputs comprehensive specifications including functional requirements in EARS format, non-functional requirements, Given/When/Then acceptance criteria, error handling tables, and

You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, implement, test thoroughly, then review.

Orchestrate end-to-end feature development from requirements to production deployment:

Build production-ready iOS features by combining ShipSwift recipes -- copy-paste-ready SwiftUI implementations covering animations, charts, UI components, and full-stack modules.

Structured product requirements documents with problem statements, user stories, and success metrics. \n \n Guides PRD structure across eight sections: problem statement, goals, non-goals, user stories, requirements (P0/P1/P2), success metrics, open questions, and timeline considerations \n Provides frameworks for user story writing, MoSCoW requirement prioritization, and acceptance criteria in Given/When/Then format \n Includes guidance on defining leading and lagging success metrics with speci

Create GitHub Issues automatically from implementation plan phases. \n \n Analyzes implementation plan files to identify phases and generates one issue per phase \n Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format \n Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed \n Includes phase details, requirements, and context in issue descriptions with appropriate labels \n

Structured PRD generation prompt for breaking down Epics into detailed feature specifications. \n \n Generates complete Product Requirements Documents in markdown format with standardized sections covering goals, user personas, stories, functional and non-functional requirements, and acceptance criteria \n Prompts for clarifying questions when insufficient information is provided, ensuring comprehensive feature definition before engineering handoff \n Organizes output into a consistent file stru

Comprehensive architecture guide for organizing React applications by features, enabling scalable development with independent teams. Contains 42 rules across 8 categories, prioritized by impact from critical (directory structure, imports) to incremental (naming conventions).

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.