skills.rest
CODE-SAURABH
CODE-SAURABHCOMMUNITY
Explore all skills by this author →
GitHub

product-engineer

Turn ambiguous product requests into focused feature plans and engineering decisions.

2|1|Updated Jul 25, 2026
Search Tags:#user flows#feature planning#technical decisions#tradeoff analysis#scope negotiation#mvp design#product engineering
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill product-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-engineer
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/product-engineer
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill product-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and technical leads turn vague product requests into focused, measurable, and technically sound solutions instead of over-engineering features that do not deliver meaningful user value.

Core Features & Use Cases

  • Feature Planning: Define user problems, success metrics, acceptance criteria, scope boundaries, risks, assumptions, and dependencies before engineering begins.
  • MVP and User Flow Design: Identify the riskiest assumptions, design testable minimum solutions, and map happy paths, errors, empty states, recovery actions, and edge cases.
  • Tradeoff and Decision Management: Compare implementation options by cost, risk, and reversibility, then document significant technical decisions using concise ADRs.
  • Scope Negotiation: Push back on low-value complexity while proposing simpler alternatives that preserve the most important user outcomes.

Quick Start

Use the product-engineer skill to turn this feature idea into an MVP plan with user outcomes, success metrics, user flows, acceptance criteria, tradeoffs, risks, and a Definition of Done.

Frequently Asked Questions about product-engineer

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

FAQPage Schema
How do I turn ambiguous product requests into focused feature plans?▼

To turn ambiguous product requests into focused feature plans, define user problems, success metrics, acceptance criteria, scope boundaries, risks, and dependencies before engineering begins. This prevents over-engineering features that do not deliver meaningful user value.

What is the best way to design an MVP with user flow analysis?▼

MVP design and user flow analysis involve identifying riskiest assumptions, designing testable minimum solutions, and mapping happy paths, errors, empty states, recovery actions, and edge cases to ensure measurable outcomes and explicit boundaries.

How do I evaluate technical tradeoffs for architecture decisions?▼

Evaluate technical tradeoffs for architecture decisions by comparing implementation options by cost, risk, and reversibility. Significant technical decisions should be documented using concise ADRs to maintain clarity and technical soundness.

Can I use scope negotiation to reduce low-value complexity in feature planning?▼

Scope negotiation helps reduce low-value complexity by pushing back on unnecessary features and proposing simpler alternatives that preserve the most important user outcomes while maintaining explicit assumptions and boundaries.

What should I include in MVP design for error and empty-state handling?▼

MVP design requires error and empty-state handling, reversibility analysis, ADR documentation, observability, and rollback planning. Mapping recovery actions and edge cases ensures technically sound engineering decisions and measurable outcomes.

When do I need ADR documentation and rollback planning for product engineering?▼

ADR documentation and rollback planning are needed when making significant technical decisions and architecture choices. They provide reversibility analysis, observability requirements, and concise records of tradeoff evaluation for engineering teams.

Related Skills

Explore More Product & Management Skills→
saranskumarsaranskumar

mvp-feature-prioritizer

Classify feature ideas into must-have, should-have, and defer categories for MVP scope.

Community
Intermediate
Productfculty-aipmProductfculty-aipm
70

user-story-decomposition

Break features or PRDs into INVEST user stories with Gherkin acceptance criteria.

Community
Intermediate
avav25avav25
2

feature-design

Convert raw feature ideas into structured PRDs with goals, user stories, and acceptance criteria.

Community
Intermediate
balajivisbalajivis
2

plan-eng-review

Review engineering implementation plans for architecture risks and missing quality requirements.

Community
Advanced