メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| 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. |
Turn an approved problem into testable requirements in the sidecar PRD.md.
PROJECT.md, product context, existing PRD, and
references/prd-quality.md.solution-architecture.Do not invent approval, metrics, research, legal requirements, or platform verification. Do not write project workflow records in the code repository.
Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.
Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.
Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.
Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.
Use when a declared frontend, backend, or integration workstream has one READY task for parent-led sequential TDD.
Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.