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/email-templates.md
View on GitHub# Email Templates
## 1. Consolidated-feedback request
```
Subject: Feedback on [project] — Round [N]
Hi [name],
Ready for your notes on V[n]. To turn these around fast and cleanly,
please send everything in one message:
• Merge feedback from everyone into a single list. If two notes
conflict, tell me which one wins.
• Add timestamps — "at 0:08 the logo feels slow."
• Describe the problem, not the fix — "the intro drags" beats "make
it faster," because it lets me solve it the right way.
• Mark must-haves vs nice-to-haves.
I'll address the full set in this round. Notes arriving separately or
later may roll into the next round. Thanks!
```
## 2. Change-order email (new request)
```
Subject: [project] — quick note on the new request
Hi [name],
Happy to help with [request] — flagging it sits outside the approved
brief/storyboard, so it's a change rather than a revision.
• Work involved: [scope]
• Cost: [amount / day estimate]
• Timeline impact: [+X days / new delivery date]
Reply "approved" to go ahead and I'll update the schedule, or we keep
to the original plan and revisit later — both are fine. Just let me
know which you'd prefer.
```
## 3. Extra-revision-round notice
```
Subject: [project] — revision rounds
Hi [name],
We've now completed the [2] revision rounds included in scope, and
the latest notes would be a [3rd] round. Glad to do it — additional
rounds run at [rate], roughly [+X days] on the schedule.
Want me to proceed on that basis, or shall we lock the current
version as final? Happy either way.
```
## 4. Stalled-approval nudge
```
Subject: [project] — waiting on your sign-off
Hi [name],
We're paused at the [storyboard] gate waiting on your approval before
the next stage can start. Our delivery date of [date] assumes sign-off
by [date]; each day of delay shifts delivery by the same amount.
A quick "approved" or your consolidated notes is all I need to keep us
on track. Thanks!
```
## 5. Scope-creep pattern reset (when many "tiny" asks have accumulated)
```
Subject: [project] — let's regroup on scope
Hi [name],
A few additions have come in since we locked the brief — each small on
its own, but together they've grown the project beyond the original
scope. So we stay on time and budget, let me bundle them:
• In original scope (no change): [list]
• New requests (change order): [list] — [cost] / [+X days]
Tell me which new items to include and I'll send an updated schedule.
Anything we drop, we can pick up in a later phase.
```
Tone rules across all: collaborative, specific, always offer a choice, always state cost and timeline impact, never accuse.
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 |