Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

product-prd

Estrellas0

Forks0

Actualizado16 de julio de 2026 a las 11:02

Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

SuShuheng

SuShuheng/making-things

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

Explorador de archivos

3 archivos

SKILL.md

readonly

name	product-prd
description	Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing.

Product PRD

Turn an approved problem into testable requirements in the sidecar PRD.md.

Read sidecar PROJECT.md, product context, existing PRD, and references/prd-quality.md.
Identify users, jobs, pain, outcomes, constraints, dependencies, and exclusions. Resolve product-changing ambiguity with the user and label reversible assumptions.
Give every requirement a stable ID, priority, and observable acceptance evidence. Cover applicable security, privacy, accessibility, reliability, performance, data, installation, update, support, and platform needs.
Separate acceptance by frontend, backend, and integration so an approved architecture can form a contract and later split disjoint workstreams.
Keep solution choices out unless they are real constraints. Record user approval in the sidecar PRD before routing to solution-architecture.

Do not invent approval, metrics, research, legal requirements, or platform verification. Do not write project workflow records in the code repository.

Más de este repositorio

mismo repositorio

handoff

SuShuheng/making-things

Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.

2026-07-160

handon

SuShuheng/making-things

Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.

2026-07-160

making-things

SuShuheng/making-things

Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.

2026-07-160

mts-more

SuShuheng/making-things

Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.

2026-07-160

mts-one

SuShuheng/making-things

Use when a declared frontend, backend, or integration workstream has one READY task for parent-led sequential TDD.

2026-07-160

mts-split

SuShuheng/making-things

Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.

2026-07-160

name	product-prd
description	Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing.

Product PRD

Turn an approved problem into testable requirements in the sidecar PRD.md.

Read sidecar PROJECT.md, product context, existing PRD, and references/prd-quality.md.
Identify users, jobs, pain, outcomes, constraints, dependencies, and exclusions. Resolve product-changing ambiguity with the user and label reversible assumptions.
Give every requirement a stable ID, priority, and observable acceptance evidence. Cover applicable security, privacy, accessibility, reliability, performance, data, installation, update, support, and platform needs.
Separate acceptance by frontend, backend, and integration so an approved architecture can form a contract and later split disjoint workstreams.
Keep solution choices out unless they are real constraints. Record user approval in the sidecar PRD before routing to solution-architecture.

Do not invent approval, metrics, research, legal requirements, or platform verification. Do not write project workflow records in the code repository.