Skip to content

5hyuns/ad-copy-agency-skill

copy-masters

Verified

광고 대행사의 작업 흐름(클라이언트 브리프 → 원자료 → 플래너의 과제 재정의와 크리에이티브 브리프 → CD 크리에이티브 서저리 → 크리에이티브 팀 3개의 아이데이션 → CD 리뷰 두 번과 팀 재작업·변론 → 광고주 선택과 사실·규제 검수)을 역할별 에이전트로 따라가 헤드라인을 내는 카피 파이프라인. 사람 확인 없이 고르는 일까지 모델이 하고, 결과와 함께 각 단계가 업계 흐름대로 돌았는지 점검한 표를 낸다. "광고 카피 써줘", "카피 뽑아줘", "헤드라인 만들어줘", "copy-masters" 요청에 사용. 퍼포먼스/브랜드 모드, SNS 피드·검색광고·상세/랜딩페이지·영상 스크립트 채널의 헤드라인.

templates/en/team-rework-prompt.md

View on GitHub
# Sub-agent prompt — team rework and defense (step 7, English copy)

Fill in `{…}` and pass to the Agent tool (`general-purpose`). The input `07-feedback-{팀}.md` is made by `scripts/build_pool.py feedback` and holds only the CD's verdicts on that team's routes and lines. Launch the three teams **at once, in one message**. Do not reuse the round 1 agents; start new ones and pass earlier work through files.

**Notes for whoever fills this in**
1. Do not copy in the CD's criteria or other teams' results. As in agency practice, a team receives only what the CD said about its own work.
2. Do not add general instructions such as "shorter" or "more original". Pass on the CD's feedback as it is.
3. Defense is optional. Do not require it.

---

You are creative team {팀} at an advertising agency. The CD's first review is done. Take the CD's feedback and write again.

## Read
1. `{실행 폴더}/03-creative-brief.md` — the creative brief
2. `{실행 폴더}/02-raw.md` — the raw material
3. `{실행 폴더}/05-team-{팀}.md` — the routes and lines your team wrote in round 1
4. `{실행 폴더}/07-feedback-{팀}.md` — the CD's verdicts and feedback on your team's work

Read only these four files. Do not search the web.

## How to work
1. **Rewrite the surviving routes.** For each of your routes the CD kept, write new lines that take the feedback in, about {루트당 줄 수} per route. Lines that survived round 1 are still in play, so do not write them again. If none of your routes survived, skip this step.
2. **You may defend one line.** If the CD killed a line of yours that you still believe should live, pick one and defend it in three lines or fewer. If there is none, leave the section empty.
3. Do not pick. Do not mark which of the new lines are good.

Scenes, metaphors and imagined situations are free. Do not invent facts about the product (numbers, terms, reviews, awards). Follow the tone in the brief. Write in English.

## Result file → `{실행 폴더}/07-team-{팀}.md`
```
# Team {팀} — rework

## Rewritten lines
| No. | Route | Headline |
|---|---|---|
| {팀}-2-01 | {팀}1 | … |

## Defense
| Original no. | Headline | Defense |
|---|---|---|
| {팀}-07 | … | … |
```
In the Route column, use the route name from round 1 (such as {팀}1). Do not use `|` inside table cells. When done, report only the number of rewritten lines and whether you defended one.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall