ワンクリックでManusで任意のスキルを実行

conversation-to-prd

スター0

フォーク0

更新日2026年7月13日 06:39

Use when the user asks to turn a conversation, feature discussion, or implementation plan into a draft PIE Elements NG PRD under docs/prds/.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

pie-framework

pie-framework/pie-elements-ng

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Conversation To PRD

Synthesize the current conversation and codebase context into a PRD draft. Do not reopen discovery by default; capture what is already known and call out gaps explicitly.

Output Target

Write or update a draft at docs/prds/<slug>/PRD.md.
Use a concise kebab-case directory slug based on the element or feature name.
Do not create Jira/GitHub issues, tracker labels, or external comments unless the user separately asks for that write.

Process

Read CONTEXT.md, docs/prds/README.md, and docs/prds/_template.md.
Re-read the conversation and any relevant local docs or code already explored.
Use PIE vocabulary from CONTEXT.md, existing PRDs, rules, and element examples, especially model/session/controller contracts, authoring surfaces, assessment accessibility, and package distribution constraints.
Identify the highest useful testing seam: prefer user-facing element behavior, controller outcomes, custom-element boundaries, package exports, and accessibility outcomes over low-level implementation seams.
Draft the PRD by filling docs/prds/_template.md; keep sections concise, but do not omit required sections.
If important details are unknown, add them to Open questions instead of interviewing before drafting.

PRD Expectations

Start as Status: **Proposal** unless the user explicitly says the contract is accepted.
Name the element or feature slug, implementation path, public package exports, consuming players/apps, and runtime environment when a contract is involved.
Separate PIE-owned behavior from host-owned persistence, identity, policy, reporting, and standards certification.
State compatibility impact for model fields, session fields, modes, controller behavior, package exports, player events/properties, and persisted or host-facing data.
Include accessibility impact, test plan, rollout notes when relevant, and release-note expectations using the repo template.

このリポジトリの他の Skills

同じリポジトリ

accessibility-reviewer-assessments

pie-framework/pie-elements-ng

Reviews educational assessment interfaces for WCAG 2.2 Level AA compliance and assessment-specific accessibility needs. Use when implementing new interactions, reviewing UI changes, or conducting accessibility audits of test-taking interfaces.

2026-07-130

grill-me

pie-framework/pie-elements-ng

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-07-130

pie-controller-reviewer

pie-framework/pie-elements-ng

Reviews a PIE controller implementation for correctness, scoring accuracy, and contract compliance. Use when implementing or reviewing controller.ts files — especially outcome(), model(), and createCorrectResponseSession().

2026-07-130

pie-element-author

pie-framework/pie-elements-ng

Implements a new PIE element (or non-trivial extension) end-to-end: PRD review → Model/Session/Controller → Svelte delivery component → authoring surface → tests. Use when adding a new @pie-element/* package or extending an existing element with a new mode or config surface.

2026-07-130

pie-prd-author

pie-framework/pie-elements-ng

Drafts or updates a PIE element PRD following the project conventions in docs/prds/README.md. Use when starting a new element that meets the PRD bar, or when a substantial change requires updating an existing PRD.

2026-07-130

source-command-grill-me

pie-framework/pie-elements-ng

Interview the user relentlessly about a plan or design until shared understanding is reached.

2026-07-130

Conversation To PRD

Synthesize the current conversation and codebase context into a PRD draft. Do not reopen discovery by default; capture what is already known and call out gaps explicitly.

Output Target

Write or update a draft at docs/prds/<slug>/PRD.md.

Use a concise kebab-case directory slug based on the element or feature name.

Do not create Jira/GitHub issues, tracker labels, or external comments unless the user separately asks for that write.

Process

Read CONTEXT.md, docs/prds/README.md, and docs/prds/_template.md.

Re-read the conversation and any relevant local docs or code already explored.

Use PIE vocabulary from CONTEXT.md, existing PRDs, rules, and element examples, especially model/session/controller contracts, authoring surfaces, assessment accessibility, and package distribution constraints.

Identify the highest useful testing seam: prefer user-facing element behavior, controller outcomes, custom-element boundaries, package exports, and accessibility outcomes over low-level implementation seams.

Draft the PRD by filling docs/prds/_template.md; keep sections concise, but do not omit required sections.

If important details are unknown, add them to Open questions instead of interviewing before drafting.

PRD Expectations

Start as Status: **Proposal** unless the user explicitly says the contract is accepted.

Name the element or feature slug, implementation path, public package exports, consuming players/apps, and runtime environment when a contract is involved.

Separate PIE-owned behavior from host-owned persistence, identity, policy, reporting, and standards certification.

State compatibility impact for model fields, session fields, modes, controller behavior, package exports, player events/properties, and persisted or host-facing data.

Include accessibility impact, test plan, rollout notes when relevant, and release-note expectations using the repo template.

name	conversation-to-prd
description	Use when the user asks to turn a conversation, feature discussion, or implementation plan into a draft PIE Elements NG PRD under docs/prds/.
disable-model-invocation	true