Menu
Use when the user asks to turn a conversation, feature discussion, or implementation plan into a draft PIE Elements NG PRD under docs/prds/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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".
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().
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.
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.
Interview the user relentlessly about a plan or design until shared understanding is reached.
| 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 |
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.
docs/prds/<slug>/PRD.md.CONTEXT.md, docs/prds/README.md, and docs/prds/_template.md.CONTEXT.md, existing PRDs, rules, and element examples, especially model/session/controller contracts, authoring surfaces, assessment accessibility, and package distribution constraints.docs/prds/_template.md; keep sections concise, but do not omit required sections.Status: **Proposal** unless the user explicitly says the contract is accepted.