How Freelancers Can Use Claude Skills to Turn Client Feedback Into One Approved Revision Brief

If Claude Skills is new to you

Claude Skills are reusable folders that Claude can load when a task matches the Skill description. A custom Skill usually includes a Skill.md file with metadata, instructions, examples, and optional supporting files. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you will create one private Skill, upload it in Claude under Customize > Skills, enable it, run a trigger test with a small mixed comment sample, and then use it to consolidate the full feedback set. The Claude Skills tool hub is useful further reading, but this page includes the setup steps needed to run the workflow.

Problem and who this is for

Client feedback rarely arrives in one clean place. It shows up in email, comment docs, chat, screenshots, and last-minute notes. If you start revising directly from the mess, you waste time, miss conflicts, and often revise the wrong thing first.

This workflow is for freelancers and consultants who need one approved revision brief before they touch the actual deliverable. The outcome is a single execution brief, not a rewrite of the client asset.

What skill you will use in this workflow

You will build a private custom Skill called revision-brief-consolidator. The Skill tells Claude how to normalize scattered comments from email, docs, and chat into one revision brief with confirmed changes, possible changes, conflicting comments, questions back to the client, and items that need explicit approval.

This task is repetitive enough to deserve a Skill because revision rounds often follow the same cleanup pattern. The Skill can encode the section structure, conflict rules, approval language, and guardrail that Claude must not decide which conflicting comment wins without explicit human direction. Before using it, prepare the current deliverable version, all comment sources, client priorities, and any scope rules for this round.

Prerequisites

• Claude with Skills available and code execution enabled.
• The current deliverable version.
• Client feedback from email, docs, chat, screenshots, or short notes.
• A file that names the current version and date.
• A short note with client priorities for this revision round.
• A clear conflict-handling rule. Example: contradictory comments stay grouped under Conflicting comments until a human asks the client to decide.
• A human review pass before the brief is sent for approval or used for execution.

How to gather the source material

1. Copy all feedback into one working folder. Keep source labels visible, such as email, Google Doc comment, Slack note, or call note.
2. Export comment-heavy docs to PDF or plain text if the live comment interface is messy.
3. Turn screenshots into readable text when possible. If you must upload screenshots, crop them tightly.
4. Create one file called deliverable-version.txt that names the current version, date, and what deliverable the comments apply to.
5. Create one file called client-priorities.txt with the top priorities the client has stated for this round.
6. Create one file called revision-scope.txt if this round only covers a subset of changes, such as copy edits, layout fixes, or final polish.
7. Remove comments about old versions unless they still apply to the current deliverable.

Build the custom skill for this workflow

Create a folder named revision-brief-consolidator. Inside it, create a file named Skill.md. Paste the starter content below into that file, then adjust it for your approval process, project type, and handoff style.

After the folder is ready, zip the revision-brief-consolidator folder itself so the ZIP contains the skill folder at its root. Do not zip loose files by themselves. In Claude, go to Customize > Skills, upload the ZIP file, and enable the Skill. Then run the trigger test below before using it on the full comment set.

---
name: revision-brief-consolidator
description: Normalize scattered client comments from email, docs, and chat into one clear revision brief with approvals, changes, conflicts, and unresolved items.
---

# Revision Brief Consolidator

Use this skill when the user needs to consolidate client comments from multiple channels into one revision brief.

## Required sections
- Confirmed changes
- Possible changes that need clarification
- Conflicting comments
- Questions back to the client

## Guardrails
- Do not resolve conflicts on your own.
- Preserve the source meaning of each comment.
- Keep a clean distinction between approved edits and proposed edits.
- Write for execution clarity, not persuasion.

## Examples
- Turn these email, comment-doc, and chat notes into one revision brief.
- Use my revision workflow and separate confirmed changes from conflicts.
- Draft a clean revision brief from these scattered comments.

Treat this as a starter template. Add your own brief sections, approval wording, done-definition rules, or client decision labels before using it on real feedback.

Optional official Anthropic skill

Anthropic's official doc-coauthoring Skill is a useful secondary reference when you need help with structured document drafting. It can be a shortcut for a one-time brief or a pattern to study.

For repeat revision work, the private revision-brief-consolidator Skill is the better fit. It can hold your exact sections, conflict-handling rules, approval language, and distinction between confirmed edits and proposed edits.

Skill-creator helper

Anthropic's official skill-creator Skill can help draft or refine this private revision Skill. Use it to improve the description, trigger examples, conflict guardrails, and section names.

Why this should be a custom skill, not a one-off prompt

Revision consolidation is repeatable and high-friction. A one-off prompt can miss conflicts, merge comments too aggressively, or forget your approval language. A Skill keeps the same sections and conflict rules available every time, which reduces prompt rewriting and keeps the brief focused on execution clarity.

Skill trigger test

After enabling the Skill, test it with a small mixed sample of comments before processing a full comment set. These prompts should cause Claude to use the revision-brief-consolidator Skill:

• Turn these client comments into one revision brief.
• Use my revision workflow and keep conflicting comments separate.
• Draft a clean revision brief from these notes without deciding which conflict wins.
• Use the revision brief Skill and separate approved changes from questions.

If Claude does not appear to use the Skill, tighten the Skill description and examples with phrases like "revision brief," "client comments," "conflicting comments," and "approved changes."

Numbered workflow steps

1. Gather and clean the source material

Put the current deliverable, deliverable-version.txt, client-priorities.txt, revision-scope.txt, and all feedback sources in one working folder. Label each comment source clearly so the brief can trace a decision back to where it came from.

Remove duplicate comments about old versions unless they still apply. Do not ask Claude to decide whether a stale comment still matters without your direction.

2. Create or enable the custom Skill for this workflow

If this is your first run, build the revision-brief-consolidator folder, add the Skill.md file, zip the folder, upload it in Customize > Skills, and enable it. If you already built the Skill, confirm it is enabled before you start.

The Skill should encode the core sections: approved changes, possible changes that need clarification, conflicting comments, questions back to the client, and items that need explicit approval. It should also encode the guardrail that Claude must not choose a winner between conflicting comments.

3. Run a quick trigger test

Use a small mixed sample first: one email comment, one doc comment, and one chat note if possible. Try:

Turn these client comments into one revision brief. Use my revision workflow, keep conflicting comments separate, and do not decide which conflict wins.

Check that Claude groups comments correctly, keeps conflicts visible, and separates confirmed changes from proposed edits. If it merges contradictions into a fake compromise, tighten the Skill guardrails before using the full comment set.

4. Run the actual workflow with the Skill active

Attach or paste the full comment set, current deliverable context, deliverable-version.txt, client-priorities.txt, and revision-scope.txt. Ask Claude to use the revision brief Skill and draft one execution brief.

Use a prompt like:

Use the revision-brief-consolidator Skill on this feedback set. Draft one approved revision brief with confirmed changes, possible changes needing clarification, conflicting comments, questions back to the client, and items needing explicit approval.

If the source set is large, ask Claude to first return a normalized comment map by source, comment meaning, status, and conflict risk. Review that map before asking for the final brief.

5. Do a human review for conflicts, scope, and approval language

Review the brief before revising the asset. Confirm that every required change appears once, conflicts are not quietly merged, and proposed edits do not become approved edits without client confirmation.

If two comments conflict, the Skill should preserve both and ask for a client decision. You decide the next action, or the client does. Claude should not decide which comment wins.

6. Save, send, or reuse the result

Save the reviewed revision brief in the project folder, task manager, or client approval thread. If you send it to the client, ask them to approve the brief before you revise the deliverable. After several rounds, update the Skill with section wording and conflict labels that consistently work for your projects.

Tool-specific instructions

Use Claude Skills for the repeatable parts of this workflow: duplicate grouping, approved-versus-proposed separation, conflict handling, questions back to the client, and execution-ready handoff language. The page-specific revision-brief-consolidator Skill should come first because revision briefs depend on your approval process and project boundaries.

For broader setup context, see the Claude Skills hub. For one-off structured drafting, Anthropic's doc-coauthoring Skill may help, but keep repeat revision consolidation in your private Skill. For drafting or refining that private Skill, use Anthropic's skill-creator as a helper.

Quality checks

1. Every change request appears only once in the brief.
2. Contradictory requests remain separate and visible.
3. The brief distinguishes confirmed changes from proposed edits.
4. Questions back to the client are specific enough to answer.
5. The brief does not expand the revision round beyond the agreed scope.
6. A teammate could execute the brief without opening five different sources.

Common failure modes and fixes

Claude collapses contradictory comments into one compromise

Fix: add a stricter guardrail to the Skill: "Conflicting comments must remain separate until a human or client chooses a direction."

The brief is still too close to the raw comments

Fix: ask Claude to rewrite each item into an execution action while preserving direct quotes only where nuance matters.

Scope creep sneaks in

Fix: include revision-scope.txt and require out-of-scope requests to sit in a separate section or client question.

Proposed edits look approved

Fix: tighten the output sections so Claude must separate confirmed changes from possible changes that need clarification.

The Skill does not trigger

Fix: update the Skill description so it includes the exact phrases you use, such as "revision brief," "client comments," "approved changes," and "conflicting comments." Then run the trigger test again.