product-engineer-agent

Design comprehensive product specifications from initial ideas.

24|2|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/michaelboeding/skills --skill product-engineer-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-engineer-agent
Source: https://github.com/michaelboeding/skills/tree/main/skills/product-engineer-agent
Command: npx skills add https://github.com/michaelboeding/skills --skill product-engineer-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams design and specify new products by coordinating multiple expert perspectives to produce a complete product specification.

Core Features & Use Cases

  • Cross-functional analysis: Five specialized agents (Industrial Designer, Mechanical Engineer, User Researcher, Manufacturing Advisor, Innovation Scout) evaluate a concept from form, function, user needs, cost, and differentiation.
  • Comprehensive output: Produces a Product Spec, Feature Matrix, BOM Estimate, Differentiation analysis, Next Steps, Concept Renders, and Engineering Drawings.
  • Workflow guidance: Provides a structured process to transform an idea into production-ready documentation.

Quick Start

Provide an initial product idea and target domain, then instruct the agent to produce a full specification. Example: "Design a lightweight portable charger with a modular battery system."

Frequently Asked Questions about product-engineer-agent

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

FAQPage Schema
How do I create a complete product specification from an initial idea?

A product specification synthesizes design, engineering, user research, manufacturing, and innovation perspectives into structured documentation. This Skill orchestrates five specialized agents to analyze your concept from each angle and produce a comprehensive spec with feature matrices, BOM estimates, and development roadmaps ready for production planning.

What does a product specification include, and why do I need all those components?

A complete product spec combines the Product Spec document, Feature Matrix, BOM Estimate, Differentiation analysis, Next Steps, Concept Renders, and Engineering Drawings. Each component addresses a different stakeholder need: the spec guides development, the matrix prioritizes features, the BOM controls costs, renders communicate vision, and drawings enable manufacturing.

Can I use this for any product domain, or are there specific types it works best for?

Product specifications apply across any domain requiring structured specs, feature matrices, BOM estimates, and development roadmaps. The cross-functional agent approach scales from consumer electronics and hardware to industrial equipment and modular systems, making it domain-agnostic as long as you can articulate an initial concept.

How does coordinating multiple expert perspectives improve my product design?

Cross-functional analysis prevents blind spots by evaluating form and aesthetics, mechanical feasibility, actual user needs, manufacturing constraints, and competitive differentiation in parallel. Synthesizing these perspectives earlier catches conflicts, reduces iteration cycles, and produces specifications that align design ambition with engineering reality and market opportunity.

What input information do I need to provide to get a full product specification?

Provide an initial product idea and target domain to start. The Skill prompts for concept details and applies its five specialized agents to extract and structure the information needed. Example: 'Design a lightweight portable charger with a modular battery system' is sufficient to trigger comprehensive specification synthesis.

Does this replace manual product spec writing, or does it prepare a draft I refine?

The Skill produces production-ready documentation including specs, matrices, renders, and engineering drawings that represent complete analysis from all five perspectives. The output serves as your authoritative specification foundation, though you may refine details, adjust roadmaps, or add domain-specific constraints based on your team's expertise.