decay-watch

Monitor Revisit Triggers in active ADR artifacts for evidence decay.

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ForgePlan/marketplace --skill decay-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decay-watch
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/fpl-skills/skills/decay-watch
Command: npx skills add https://github.com/ForgePlan/marketplace --skill decay-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires forgeplan, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies Revisit Triggers in active ADR artifacts, reporting on evidence decay and triggering necessary human verification or ADR updates.

Core Features & Use Cases

  • Scan Active ADR Artifacts: Automates the search for Revisit Triggers and Compliance sections within active ADR artifacts.
  • Evidence Decay Detection: Identifies and reports triggers that have fired, those that require human verification, and stale ADRs.
  • Use Case: Regularly running this Skill as a part of project sessions or weekly reviews helps maintain the relevance and up-to-date status of ADRs.

Quick Start

To check for evidence decay, run the /decay-watch command in your ForgePlan workspace.

Frequently Asked Questions about decay-watch

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

FAQPage Schema
How do I monitor evidence decay in active ADR artifacts?

Detecting evidence decay in ADR artifacts involves scanning active documents for triggered Revisit Triggers and compliance sections. This process identifies stale decisions, reporting triggered events and pending items that necessitate human verification or ADR updates.

What is an ADR Revisit Trigger and when does it fire?

An ADR Revisit Trigger is a predefined condition within an Architecture Decision Record that signals evidence decay. It fires when specific time-based or event-based criteria are met, indicating that the decision context requires human verification or an ADR update.

How do I automate checking ADR freshness during project reviews?

Automating ADR freshness checks during project reviews involves running a decay monitor against active ADR artifacts. This automatically searches for fired Revisit Triggers and compliance items, generating a report of stale decisions requiring updates.

Do I need a ForgePlan API connection to track ADR decision traceability?

Tracking ADR decision traceability for evidence decay requires ForgePlan API access. The API connection is necessary for the monitoring process to retrieve active ADR artifacts, scan Revisit Triggers, and apply modifications to maintain ADR freshness.

What is the best way to maintain ADR freshness in software engineering?

Maintaining ADR freshness is best achieved by regularly scanning for evidence decay and triggered events. Running automated checks during weekly reviews identifies stale decisions and pending compliance items, prompting necessary human verification and ADR updates.

Why does ADR monitoring report stale decisions during evidence decay checks?

ADR monitoring reports stale decisions during evidence decay checks because active artifacts contain Revisit Triggers that have fired. The monitoring identifies these triggered events and pending compliance items, flagging decisions that no longer hold valid evidence.