agreement-review

Evaluate agreement relevance and determine renewal, revision, or sunset actions.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/JadeZaher/neos-operating-system --skill agreement-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agreement-review
Source: https://github.com/JadeZaher/neos-operating-system/tree/main/neos-core/layer-01-agreement/agreement-review
Command: npx skills add https://github.com/JadeZaher/neos-operating-system --skill agreement-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents governance decay by ensuring agreements are regularly re-validated against current conditions, preventing them from becoming stale, outdated, or misaligned.

Core Features & Use Cases

  • Periodic Review: Automatically schedules and facilitates the review of agreements based on set dates or trigger events.
  • Outcome Determination: Guides a review body to assess relevance, appropriateness, and consistency, leading to decisions to renew, revise, or sunset agreements.
  • Use Case: When a community space agreement's review date arrives, this skill convenes the current residents to evaluate its terms, ensuring it still meets their needs and aligns with current community policies, and then either renews it, initiates an amendment for necessary changes, or sunsets it if it's no longer serving its purpose.

Quick Start

Initiate a review for the agreement with ID 'AGR-SHUR-2026-003'.

Frequently Asked Questions about agreement-review

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

FAQPage Schema
How do I manage a periodic agreement review cycle for governance compliance?

Periodic agreement review cycles are managed by evaluating current relevance, checking for staleness or conflict, and producing a review outcome to either renew, revise, or sunset the agreement. This prevents governance decay by re-validating terms against current conditions.

When should I initiate an agreement renewal or sunset process?

Agreement renewal or sunset processes should be initiated when scheduled review dates arrive, participant requests are made, or threshold events occur. The review evaluates relevance and consistency to determine if terms should be renewed, revised, or sunset.

What data is needed to check agreements for staleness or conflict?

Checking agreements for staleness or conflict requires agreement data, participant feedback, conflict logs, and registry data. These inputs determine whether an agreement remains aligned with current community policies and conditions.

Can I review organizational culture codes and space agreements using the same process?

Yes, the same review process applies to all agreement types, including space, access, organizational, stewardship, culture codes, and the UAF. It evaluates relevance and appropriateness to guide decisions across all agreement categories.

What is the best way to prevent governance decay in community agreements?

Preventing governance decay requires regularly re-validating agreements against current conditions through scheduled or triggered reviews. This ensures terms remain relevant, appropriate, and consistent, leading to timely renewal, revision, or sunset actions.

How do I start a review for a specific agreement ID?

To start a review for a specific agreement, initiate the process using the agreement ID. The system then convenes relevant participants to evaluate the terms and produce a renewal, revision, or sunset outcome.