메뉴
The Seven Sweeps framework for reviewing and enhancing existing copy. Focuses on clarity, voice/tone, benefits, proof, specificity, emotion, and risk reversal.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | copy-editing |
| description | The Seven Sweeps framework for reviewing and enhancing existing copy. Focuses on clarity, voice/tone, benefits, proof, specificity, emotion, and risk reversal. |
Check for project context first:
Before editing, read .agent/rules/10_project.md. Use the defined Vision, Goals, Users, and Constraints from that context to guide your edits. Only ask the user for information not already covered in that document.
Good copy editing isn't about rewriting—it's about enhancing. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once.
Key principles:
Edit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.
Focus: Can the reader understand what you're saying?
What to check:
Common clarity killers:
Process:
After this sweep: Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact.
Focus: Is the copy consistent in how it sounds?
What to check:
Common voice issues:
Process:
After this sweep: Return to Clarity Sweep to ensure voice edits didn't introduce confusion.
Focus: Does every claim answer "why should I care?"
What to check:
The So What test: For every statement, ask "Okay, so what?" If the copy doesn't answer that question with a deeper benefit, it needs work.
❌ "Our platform uses AI-powered analytics" So what? ✅ "Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time"
Common So What failures:
Process:
After this sweep: Return to Voice and Tone, then Clarity.
Focus: Is every claim supported with evidence?
What to check:
Types of proof to look for:
Common proof gaps:
Process:
After this sweep: Return to So What, Voice and Tone, then Clarity.
Focus: Is the copy concrete enough to be compelling?
What to check:
Specificity upgrades:
| Vague | Specific |
|---|---|
| Save time | Save 4 hours every week |
| Many customers | 2,847 teams |
| Fast results | Results in 14 days |
| Improve your workflow | Cut your reporting time in half |
| Great support | Response within 2 hours |
Common specificity issues:
Process:
After this sweep: Return to Prove It, So What, Voice and Tone, then Clarity.
Focus: Does the copy make the reader feel something?
What to check:
Emotional dimensions to consider:
Techniques for heightening emotion:
Process:
After this sweep: Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.
Focus: Have we removed every barrier to action?
What to check:
Risk reducers to look for:
Common risk issues:
Process:
After this sweep: Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity.
Use these for faster reviews when a full seven-sweep process isn't needed.
Cut these words:
Replace these:
| Weak | Strong |
|---|---|
| Utilize | Use |
| Implement | Set up |
| Leverage | Use |
| Facilitate | Help |
| Innovative | New |
| Robust | Strong |
| Seamless | Smooth |
| Cutting-edge | New/Modern |
Watch for:
After completing all 7 sweeps, present findings in this format:
COPY REVIEW SUMMARY
───────────────────
Sweep 1 (Clarity): X findings
Sweep 2 (Voice): X findings
Sweep 3 (So What): X findings
Sweep 4 (Proof): X findings
Sweep 5 (Specificity): X findings
Sweep 6 (Emotion): X findings
Sweep 7 (Risk): X findings
Overall: CLEAN | NEEDS WORK | MAJOR REWRITE
Top 3 Priority Edits: [numbered list]
When editing collaboratively:
This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.
copy-editing to review and improve after your first draft is complete.Structured brainstorming for exploring new features or solving complex problems
Scope, architect, and plan new tasks
Multi-angle code review before merging
Summarize the day's work and put it in context
Wrap up work — atomic commits and push to origin
Full end-to-end (E2E) testing skill utilizing the browser. Make sure to use this skill whenever the user asks to "test the app", "run end to end tests", "verify the UI", "check if the app works", or wants you to use the browser to interact with and test the application flow. This skill orchestrates creating a test plan, getting user approval, navigating the application using the browser, independently fixing obstacles, and generating a progressive test report.