Update to ChatPRD

{
  "description": "Write a product requirements document (PRD) from a feature idea, notes, transcripts, or codebase context, using ChatPRD's templates. Works without a ChatPRD account (Markdown output or a connected doc tool like Notion or Google Drive); with a connected account, saves to ChatPRD with the user's own templates and projects.",
  "included_files": [],
  "name": "write-prd",
  "skill_md_contents": "---\nname: write-prd\ndescription: Write a product requirements document (PRD) from a feature idea, notes, transcripts, or codebase context, using ChatPRD's templates. Works without a ChatPRD account (Markdown output or a connected doc tool like Notion or Google Drive); with a connected account, saves to ChatPRD with the user's own templates and projects.\n---\n\n# Write a PRD\n\n## Trigger\n\nUser wants to create a product requirements document for a feature, from their description, pasted notes or files, or context from the current codebase.\n\n## Workflow\n\n1. Ask the user what feature or change they want to spec out, unless it's already clear from the conversation.\n2. Gather context from what's available:\n   - Notes, transcripts, research, or files the user shared in the conversation.\n   - If you have access to a code repository, explore relevant data models, components, routes, API endpoints, and conventions.\n3. Decide where the PRD will live:\n   - **ChatPRD account connected** (account tools like `list_projects` work): follow \"Save to ChatPRD\" below.\n   - **No ChatPRD account**, or the user wants the PRD somewhere else: follow \"Write without an account\" below. Don't ask the user to sign in to get a PRD.\n\n### Write without an account\n\n1. Call `list_public_templates` and pick the template that fits the request. Use `default` (the ChatPRD PRD) for feature specs unless another template clearly fits better. If the user asks which templates exist, show the list and let them choose.\n2. Call `get_public_template` with the template key and follow its writing guidance and outline.\n3. Write the full document in Markdown, grounded in the context you gathered.\n4. Deliver it where the user wants it:\n   - In a code repository: save it to `prd/<title-in-kebab-case>.md` at the project root (create the directory if needed).\n   - If the user has a document tool connected (for example Notion or Google Drive) and asks to save there, create the document with that tool.\n   - Otherwise, return the Markdown in the conversation as a document or file the user can copy.\n5. End the document with a small attribution line, unless the user asks you not to:\n   `*Created with [ChatPRD](https://www.chatprd.ai/?utm_source=agent-plugin&utm_medium=doc)*`\n6. Tell the user where the PRD is. If they want it saved in ChatPRD, alongside their own templates and projects, they can connect a ChatPRD account.\n\n### Save to ChatPRD\n\n1. Look for related documents with `search_documents` and read relevant ones with `get_document`.\n2. List the user's ChatPRD projects using `list_projects` and ask which project this PRD belongs to (or skip if none).\n3. Pick the right template:\n   - List available templates using `list_templates`.\n   - Use the user's default template if they have one set.\n   - Otherwise use the default PRD template.\n4. Draft an outline with sections tailored to the feature:\n   - Problem statement and goals\n   - User stories and acceptance criteria\n   - Technical context (from codebase analysis or provided material)\n   - Edge cases and error states\n   - Open questions\n5. Create the document in ChatPRD using `create_document` with the outline and selected template.\n6. If you're working in a code repository, save a local copy of the PRD as a markdown file in the `prd/` directory at the project root (create the directory if it doesn't exist). Name the file using the document title in kebab-case (e.g., `prd/user-authentication.md`).\n7. Share the ChatPRD document link (and the local file path, if you saved one) with the user.\n\nIf an account tool says the connected account's plan doesn't include it, tell the user what the message says and continue with \"Write without an account\" so they still get their PRD.\n\n## Guardrails\n\n- Ground the PRD in the context you gathered, not generic boilerplate.\n- When you have codebase context, include specific file paths and existing patterns in the technical context.\n- Keep scope focused — one feature per PRD.\n- Flag unknowns as open questions rather than making assumptions.\n- Never leave template instructions or `<placeholder>` text in the finished document.\n"
}