intent-changes

Organize structured change proposals for design documents through a PR-like review workflow.

15|5|Updated Jan 20, 2026

Search Tags:#documentation #collaboration #proposal #design-doc #change-management #review-workflow

Ready to run

npx skills add https://github.com/ArcBlock/idd --skill intent-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-changes
Source: https://github.com/ArcBlock/idd/tree/main/skills/intent-changes
Command: npx skills add https://github.com/ArcBlock/idd --skill intent-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize structured change proposals for design documents and track decisions through a PR-like review workflow.

Core Features & Use Cases

Structured Change Proposals: Each change is tracked as an independent proposal with fields like ID, Type, Status, Target, Before/After, and a formal Decision record.
Lifecycle and Collaboration: Proposals flow from PENDING to ACCEPTED/REJECTED; approved changes can be finalized and applied to the source document with an auditable history.
Commands and Workflow: Use commands like /intent-changes start, propose, accept, reject, status, and finalize to manage the end-to-end review of a design doc.
Use Case: A design doc is reviewed collaboratively; proposals are discussed, accepted or rejected, and finally applied to produce a coherent updated document.

Quick Start

Start a review session by running /intent-changes start <file>.

Frequently Asked Questions about intent-changes

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

FAQPage Schema

How do I manage collaborative design document reviews with a structured change proposal workflow?▼

A structured change proposal workflow organizes design document reviews by tracking each change as an independent proposal with fields like ID, Type, Status, and Target. This enables collaborative discussion, explicit decisions, and auditable history before finalizing updates to the source document.

What is a PR-like review workflow for design docs and when do I need it?▼

A PR-like review workflow for design docs applies a lifecycle of PENDING, ACCEPTED, REJECTED, and APPLIED states to proposed changes. You need this process when collaborating on requirements or architecture documents to ensure proposed modifications are formally reviewed and tracked before integration.

How do I start a review session and track decisions for a design doc?▼

Start a review session for a design doc by running the start command on your target file. You can then use specific commands to propose changes, accept or reject them, check status, and finalize approved proposals to apply them to the source document.

Can I track rejected and accepted proposals separately during a design review?▼

Yes, you can track accepted and rejected proposals separately during a design review. The workflow enforces a lifecycle where proposals move from PENDING to either ACCEPTED or REJECTED, ensuring every decision is formally recorded with an explicit ID and target.

What's the best way to finalize approved changes and apply them to the source document?▼

The best way to finalize approved changes is to use the finalize command after proposals have been accepted through the review workflow. This applies the approved modifications to the source design document while maintaining an auditable history of all decisions.