update

Apply consensus from Foundry annotation threads to design documents.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill update-danhannah94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/danhannah94/claymore-plugins/tree/main/lean/skills/update
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill update-danhannah94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill locks in decisions from Foundry annotation threads by updating the active document to reflect consensus, closes discussions, and moves settled decisions to decisions.md.

Core Features & Use Cases

  • Read annotation threads to identify agreement between human and AI responses.
  • Update the deepest applicable section of the document via Foundry APIs, preserving annotations on related sections.
  • Resolve completed threads and graduate decisions into decisions.md when appropriate.
  • Provide a concise summary of changes and any unresolved threads for follow-up.

Quick Start

Provide the target document path (or use next.md by default) and run /update to apply the consensus changes.

Frequently Asked Questions about update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a design doc based on Foundry annotation threads?

To update a design doc based on Foundry annotation threads, this Skill applies consensus from the discussions by writing the agreed changes directly to the deepest applicable document section via Foundry APIs.

How do I lock in decisions from Foundry annotations into a decisions.md file?

To lock in decisions from Foundry annotations, this Skill graduates settled discussion threads into your decisions.md file and automatically resolves the completed annotation threads across the document.

Does updating documents from Foundry annotations require API access?

Yes, updating documents from Foundry annotations requires Foundry API access to read and write doc sections, allowing the tool to apply consensus changes while preserving existing annotations on related sections.

What happens to Foundry annotation threads without clear agreement when updating a design doc?

When updating a design doc, Foundry annotation threads without clear agreement are safely skipped, and the Skill provides a concise summary of these unresolved threads for manual follow-up.

What is the best way to resolve completed annotation threads in Foundry projects?

The best way to resolve completed annotation threads in Foundry projects is to use this Skill to automatically close discussions once consensus is detected, updating the active document and graduating decisions to decisions.md.