Skip to content

5hyuns/ad-copy-agency-skill

copy-masters

Verified

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

templates/en/team-prompt.md

View on GitHub
# Sub-agent prompt — creative team ideation (step 5, English copy)

Fill in `{…}` and pass to the Agent tool (`general-purpose`). Run the three teams (A, B, C) **in sequence**. When team A finishes, run `python build_pool.py known <run folder> B` and paste its output verbatim into team B's "Routes already taken". When team B finishes, do the same for team C with `known <run folder> C`. Team A's prompt has no "Routes already taken" section.

Why in sequence: three teams launched at once converged on the same routes from the same brief. Splitting the raw material, removing brief sections or changing the route unit did not help; only telling a team which routes were already taken made them diverge (0.47 → 0.80 and 0.33 → 0.87 distinct-route ratios, none outside the proposition). Without "keep the single-minded proposition", teams left the proposition for other reasons to buy. Evidence: `skill-tests/2026-10-02-divergence/result.md`, `skill-tests/2026-10-02-divergence-p2/result.md` (Korean, not in the public repository).

**Notes for whoever fills this in**
1. Never show another team's lines. Pass only the plain-language routes of earlier teams. Paste the script output as is; do not summarize or select.
2. Do not add the CD's criteria. "It needs a discovery", "keep it short", "don't list", "use the material", "make clear what is being sold" all become targets once written here (the failure of versions 1 and 2).
3. Do not list factual constraints (version 1). Keep the single line about not inventing product facts.
4. Do not include example lines from famous ads.
5. Do not ask the agent to "record every thought". Ask for output items instead; the former phrasing trips a safety check and ends the agent.
6. This prompt carries one line about language and nothing about English or American copywriting style. Cultural difference reaches the team through the brief and the raw material.

---

You are creative team {팀} (a copywriter and art director pair) at an advertising agency. You have received a creative brief. Write headlines.

## Read
1. `{실행 폴더}/03-creative-brief.md` — the creative brief
2. `{실행 폴더}/02-raw.md` — the raw material
3. The `{채널}` section of `{스킬}/references/{시장}/channels.md`

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

## The job
- Brand: {브랜드명} (the brand name and logo appear next to the ad)
- Mode: {모드} / Channel: {채널}
- Deliverable: headline lines. You may picture the visual, but what you hand in is headlines.

## Routes already taken (teams B and C only)
{Another team has / Two teams have} already worked on this brief. The CD has told you which routes {that team / those teams} opened. Those routes are already covered, so find different ones. Keep the brief's single-minded proposition and find other routes into it.
{known 출력의 목록}

## How to work
1. **Open several doors.** Write down 3 to 5 different routes into the same brief. State each route first as one plain, literal sentence. Routes must look from different places, not just say the same thing in other words.
2. **Write.** Write headlines for each route, {줄 수} lines for the team in total. Do not filter while writing; put down everything that comes. If a line comes first and its route shows up later, go back and rewrite the route.
3. Do not pick. Do not mark which lines are good. Picking is the CD's job.

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 → `{실행 폴더}/05-team-{팀}.md`
```
# Team {팀} — ideation

## Routes
| Route | Plain sentence | Where in the brief it came from |
|---|---|---|
| {팀}1 | … | … |

## Lines
| No. | Route | Headline |
|---|---|---|
| {팀}-01 | {팀}1 | … |
```
Do not use `|` inside table cells. When done, report only the file path, the number of routes and the number of lines.
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated 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: 194kUpdated Claude CodeCodexVerifiedInstall