iart-ai/freelance-motion-skills / skills/client-revisions
client-revisions
VerifiedThis skill should be used when the user asks to "stop scope creep", "limit revision rounds", "write SOW revision language", "the client keeps asking for changes", "how do I say this is out of scope", "translate vague feedback", "client said make it pop", or "write a change-order email". It provides revision-cap contract language, a consolidated-feedback request, a vague-feedback translator, and a polite out-of-scope email.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 0 B |
| SKILL.md | skill md | 11.2 KB |
| references/email-templates.md | markdown | 2.6 KB |
| references/feedback-translator.md | markdown | 2.7 KB |
| references/sow-clauses.md | markdown | 2.6 KB |
references/sow-clauses.md
View on GitHub# SOW Clauses (full)
## Revision section
```
REVISIONS & APPROVALS
1. Included rounds. This engagement includes [2] rounds of revisions
on the agreed deliverables.
2. Definition of a round. A "round" is a single, consolidated set of
feedback gathered from all stakeholders, delivered in one document,
and addressed by us in full before the next version is issued.
Feedback delivered piecemeal or across separate messages may be
treated, at our discretion, as separate rounds.
3. What is a revision (included). Adjustments to elements already
approved at brief and storyboard stage: timing and pacing, colours
within the agreed palette, approved copy edits, and corrections of
errors or technical glitches.
4. What is a new request (not included). New scenes; additional
runtime; new creative concepts or directions; additional formats,
durations, or aspect ratios; assets not previously supplied; and
any feedback reversing a previously approved decision. New requests
are handled as change orders (clause 7).
5. Additional rounds. Revision rounds beyond those included are billed
at [day rate / fixed fee per round] and may extend the timeline.
6. Approval gates. Work proceeds through sign-off stages: brief →
storyboard/animatic → first animation → final. Approval at each gate
locks that stage. Reopening a locked stage is a new request.
7. Change orders. Any new request will be quoted (cost + timeline
impact) in writing before work proceeds. Work on the new request
begins only on written approval.
```
## Approval-gate language (standalone)
```
SIGN-OFF GATES
Each stage below must be approved in writing before the next begins.
Approval locks that stage:
• Brief — creative intent and message.
• Storyboard / animatic — structure, scenes, pacing, copy.
• First animation — motion, timing, colour.
• Final — delivery-ready files.
Changes to a locked stage are change orders, not revisions, because
later work was built on the approved version.
```
## "Round" definition variants
- **Strict**: "A round is one consolidated feedback document. Separate messages count as separate rounds." (Use with clients prone to drip-feeding.)
- **Standard**: "A round is one consolidated set of feedback addressed in full." (Default.)
- **Generous**: "Minor follow-ups within 24h of returning notes fold into the same round." (Use for trusted, long-term clients.)
## Kill / pause clause (optional)
```
If the project is paused by the client for more than [10] working days,
remaining work is rescheduled subject to availability, and the balance
for work completed to date becomes payable.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |