Update to Rivora

{
  "description": "Implement a feature in the open repository from a published Rivora handoff. Use when the user names a Rivora feature, product, handoff id, or version pin, or asks to build from Rivora.",
  "included_files": [],
  "name": "implement-from-handoff",
  "skill_md_contents": "---\nname: implement-from-handoff\ndescription: Implement a feature in the open repository from a published Rivora handoff. Use when the user names a Rivora feature, product, handoff id, or version pin, or asks to build from Rivora.\n---\n\n# Implement from a Rivora handoff\n\nRivora is the source of the approved feature pack. The open repository is the code to change. Read the handoff through the Rivora MCP server, then implement only what that pinned version says.\n\n## Before changing code\n\n1. Resolve one handoff.\n   - If the user gives a handoff id or version pin, call `get_handoff`.\n   - Otherwise call `find_handoffs` with the feature name and, when known, the product name. Use the single latest match. If several matches remain, ask which one to use.\n2. Read the sections this change needs with `get_handoff_section`. Prefer, in this order, the ones that exist on the handoff:\n   - `cursor_coding_agent_handoff`\n   - `implementation_handoff`\n   - `frontend_ux_specification`\n   - `backend_platform_specification`\n   - `data_and_memory_specification`\n   - `jira_delivery_mapping`\n   - `current_product_impact_map`\n   - `architecture_module_impact_map`\n   - `feature_intent_and_problem_framing`\n   - `executive_summary`\n3. Call `list_handoff_open_questions`. Treat unresolved questions as scope you must not invent past.\n4. Call `list_handoff_citations` when a requirement needs its source. Use `search_handoff_evidence` only to search evidence frozen in that same handoff.\n5. Tell the user the `version_pin` and `content_hash` from `get_handoff` before editing files.\n\n## While implementing\n\n- Follow the pinned handoff. A later change in the live Feature Pack is a different version.\n- Keep draft or unapproved material out of the implementation. The published handoff is the approved bundle.\n- Stay inside the open repository. Do not edit Rivora Product OS, its approved sections, or another product's code.\n- When an open question blocks a decision, stop and ask the user. Do not fill the gap with a guess.\n\n## Sending a proposal back\n\nCall `propose_handoff_changes` only when the user explicitly asks to send a proposal to Rivora. If their Rivora sign-in did not include proposal access, the tool returns a permission error. Stop there and tell them Rivora did not grant proposal submission for this login. A successful call records a proposal for a person to review. It does not change the approved handoff.\n"
}