Update to ChatPRD

{
  "description": "Update an existing ChatPRD document with new decisions, feedback, or what was actually built. Use when the user wants to revise a PRD, add or change a section, or capture implementation decisions, trade-offs, and deviations after building.",
  "included_files": [],
  "name": "update-prd",
  "skill_md_contents": "---\nname: update-prd\ndescription: Update an existing ChatPRD document with new decisions, feedback, or what was actually built. Use when the user wants to revise a PRD, add or change a section, or capture implementation decisions, trade-offs, and deviations after building.\n---\n\n# Update PRD\n\n## Trigger\n\nUser wants to change an existing PRD — to add a section, apply review feedback, record new decisions, or match what was actually built.\n\n## Workflow\n\n1. Find the relevant PRD:\n   - Ask the user which document to update, or search using `search_documents`.\n   - In a code repository, also check the local `prd/` directory.\n2. Fetch the current PRD content using `get_document`.\n3. Gather what should change:\n   - Changes the user described in the conversation.\n   - If the user just finished building the feature in a code repository, review the git diff against the base branch and compare it with the spec: requirements implemented as specified, deviations and their reasons, deferred scope, and new edge cases.\n4. Draft the change:\n   - Mark completed requirements and document deviations with rationale.\n   - Add a \"What was actually built\" section if the implementation changed significantly.\n   - Move deferred items to a \"Future work\" section.\n5. Show the user a short summary of the planned edits and get confirmation.\n6. Update the document using `update_document`. This tool replaces the whole document, so pass the complete rewritten markdown in `contentMarkdown`, keeping every section you didn't intend to change, and include a brief `summary` of the edits.\n7. If a local copy exists in `prd/`, update it to match.\n\n## Guardrails\n\n- Always confirm before calling `update_document`.\n- Preserve the original PRD structure — add to it, don't rewrite it.\n- Never drop existing content unless the user asked to remove it.\n- Be honest about deviations — they're documentation, not failures.\n\n## Output\n\n- Updated PRD in ChatPRD with document link\n- Updated local copy in `prd/`, if present\n- Summary of changes made to the document\n"
}