client-revisions

Classify client feedback and generate change-order language for motion design projects.

1|1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/iart-ai/freelance-motion-skills --skill client-revisions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-revisions
Source: https://github.com/iart-ai/freelance-motion-skills/tree/main/skills/client-revisions
Command: npx skills add https://github.com/iart-ai/freelance-motion-skills --skill client-revisions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps motion designers control revision rounds, prevent scope creep, and keep client feedback from turning into unpaid rework or endless back-and-forth.

Core Features & Use Cases

  • Revision-Cap Language: Adds clear SOW wording that defines a revision round, sets a round limit, and separates approved changes from new requests.
  • Feedback Triage: Classifies notes as revision, new request, or vague feedback before work begins so only in-scope changes are executed.
  • Client Communication Templates: Produces consolidated-feedback requests, vague-feedback follow-up questions, extra-round notices, and polite change-order emails.
  • Use Case: A client says “make it pop,” adds a square version, and asks for another scene; this Skill translates the vague note, flags the new requests, and drafts the right email response.

Quick Start

Ask the client-revisions skill to turn this project’s latest feedback into a revision plan, a scope check, and a change-order email if anything is out of scope.

Frequently Asked Questions about client-revisions

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

FAQPage Schema
How do I stop scope creep on motion design revisions?

Prevent scope creep by classifying stakeholder feedback as revisions or new requests, enforcing SOW revision caps, and generating written change-order language with cost-and-timeline impact for out-of-scope work.

How do I handle vague client feedback like make it pop?

Handle vague client feedback by consolidating stakeholder notes and generating targeted follow-up questions that translate ambiguous notes into actionable, in-scope motion design revisions.

What is the best way to write SOW clauses for revision rounds?

Write SOW clauses for revision rounds by defining what constitutes a revision, setting a firm round limit, and separating approved changes from new requests to prevent unpaid rework.

How do I draft a polite out-of-scope response for extra revision requests?

Draft a polite out-of-scope response by flagging the new request, noting the extra revision round, and generating a change-order email that states the written cost-and-timeline impact.

When do I need to issue a change order for motion design feedback?

Issue a change order for motion design feedback when client notes exceed the SOW revision caps, reopen approval gates, or introduce new requests beyond the originally approved project scope.

Can I consolidate feedback from multiple stakeholders before starting revisions?

Yes, you can consolidate feedback from multiple stakeholders by merging timestamped notes, classifying each item as a revision or new request, and creating a unified revision plan before work begins.