Tech Product Manager (Behavior & Design)

Generates Gherkin behavioral specifications and Mermaid screen designs from PRDs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hubble-inc/demo-nego --skill tech-product-manager-behavior-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tech Product Manager (Behavior & Design)
Source: https://github.com/Hubble-inc/demo-nego/tree/main/.cursor/skills/create-tech-prd
Command: npx skills add https://github.com/Hubble-inc/demo-nego --skill tech-product-manager-behavior-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level Product Requirements Documents (PRDs) into detailed, actionable "behavioral specifications" (BDD) and "screen designs" that engineers can implement without needing to decipher ambiguous requirements.

Core Features & Use Cases

  • Behavioral Specification (BDD): Generates Gherkin-formatted scenarios (Given/When/Then) to precisely define system interactions from a user's perspective.
  • Screen Design Specification: Outlines UI elements, states, and user flows using Mermaid diagrams.
  • Use Case: A product manager provides a PRD for a new e-commerce checkout feature. This Skill generates detailed BDD scenarios for all user interactions (adding items, applying discounts, payment) and screen mockups, ensuring clarity for the development team.

Quick Start

Use the create-tech-prd skill to generate a behavioral specification and screen design for the user login feature based on the provided PRD.

Frequently Asked Questions about Tech Product Manager (Behavior & Design)

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

FAQPage Schema
How do I convert a PRD into Gherkin BDD scenarios?

To convert a PRD into Gherkin BDD scenarios, use this Skill to generate Given/When/Then behavioral specifications from high-level product requirements. It translates user-facing system interactions into precise scenarios that engineers can implement immediately.

What is the best way to generate screen design documents from product requirements?

Generating screen design documents from product requirements is done by outlining UI elements, states, and user flows using Mermaid diagrams. This Skill processes PRDs to produce visual screen specifications without including technical implementation details.

Can I break down large product features into smaller requirement files?

Yes, you can break down large product features into smaller requirement files. This Skill supports atomic decomposition of features, splitting complex PRDs into manageable behavioral specification and screen design files for easier development.

Does this Skill include QA acceptance criteria in the behavioral specifications?

Yes, the behavioral specifications generated include QA acceptance criteria. When processing a PRD, the Skill outputs Gherkin-formatted scenarios that define specific user interactions and system states to ensure testing clarity.

How do I define system behavior without specifying technical implementation?

To define system behavior without technical implementation, this Skill focuses purely on user-facing interactions. It transforms PRDs into behavioral specifications and screen designs, explicitly omitting underlying technical details to ensure engineers understand what to build, not how.