pdm-design-doc

Convert user ideas and problem fragments into Design Docs and specifications.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/hico-mrmgn/Skills --skill pdm-design-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdm-design-doc
Source: https://github.com/hico-mrmgn/Skills/tree/main/plugins/pdm-design-doc/skills/pdm-design-doc
Command: npx skills add https://github.com/hico-mrmgn/Skills --skill pdm-design-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PdM Design Doc 作成ワークフローを提供し、アイデア・ユーザーの声・問題の断片からDesign Docと仕様書まで一貫して作成します。

Core Features & Use Cases

  • Phase 1(ディスカッション)でアイデアを引き出し、問題を可視化します。
  • Phase 2(Design Docドラフト)で要件・ゴールを整理したドラフトを生成します。
  • Phase 3(仕様書変換)で仕様書フォーマットへ落とし込み、実装の指針を提供します。

Quick Start

アイデアとユーザーの声を入力してこのスキルに渡し、Design Docと仕様書を作成します。

Frequently Asked Questions about pdm-design-doc

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

FAQPage Schema
How do I turn product ideas and user feedback into a design doc and specification?

To turn ideas and user feedback into a design doc and specification, you can use a structured workflow that extracts requirements through discussion, drafts a design doc, and converts it into a specification with user stories and UX flows.

What is the best way to structure a design doc with user stories and UX flows?

The best way to structure a design doc with user stories and UX flows is to follow a phased workflow: ideation and problem visualization, drafting goals and requirements, and finalizing measurable success metrics and technical notes.

Can I generate measurable success metrics and technical notes from raw problem fragments?

Yes, you can generate measurable success metrics and technical notes from raw problem fragments by processing them through a discussion phase that visualizes the problem before drafting the final specification.

Do I need a specific format to input user stories and ideas for product management workflows?

No specific input format is required for user stories and ideas in product management workflows; you simply provide raw ideas and user voices, and the system extracts and structures them into a formal design doc template.

What distinguishes a phased design doc workflow from a standard product specification template?

A phased design doc workflow distinguishes itself by guiding the process through discussion, drafting, and specification conversion to produce structured outputs like UX flows and technical notes, rather than just providing a static template.

When should I not use an automated design doc generator for requirements gathering?

You should not use an automated design doc generator when your requirements are already fully defined and finalized, as the workflow is specifically built to extract and structure ideas from raw, incomplete problem fragments.