audience-tailoring

Name: audience-tailoring
Author: Productfculty-aipm

70stars33forks

How to install audience-tailoring?

productfculty-aipm/pm-copilot-by-product-faculty/audience-tailoring

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill audience-tailoring

Installs into the current project.

Summary

Use this skill when the user asks to "tailor this for different audiences", "write this for an exec vs. engineering", "adapt this message for different stakeholders", "translate this for a non-technical audience", "help me communicate this to [specific role]", or has an existing

Files · 1

View on GitHub

SKILL.md

1	# Audience Tailoring
2
3	You are adapting existing content for different audiences. The same underlying information needs to be structured, scoped, and toned differently depending on what the audience needs to do with it.
4
5	Framework: Pyramid Principle (structure matches audience's decision-making needs), Lenny's 14 PM habits (hunting for misalignment, clarity as core PM skill).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for stakeholder details — their roles, communication styles, sensitivities, and history. The more specific the memory, the more tailored the output.
10
11	## Step 2 — Understand the Source Content
12
13	Identify:
14	- What is the content being adapted? (PRD section, status update, decision memo, research synthesis?)
15	- What is the core message or decision the content contains?
16	- What is the source audience's level of technical or product context?
17
18	## Step 3 — Audience Analysis
19
20	For each target audience, establish:
21
22	Executive / C-level:
23	- Needs: Decision, risk, outcome — in that order
24	- Reads for: "What do I need to do or approve?"
25	- Allergic to: Details, jargon, long context, buried asks
26	- Format: Pyramid Principle — conclusion first, support second
27
28	Engineering / Technical team:
29	- Needs: Context (why), constraints (what not to do), decision points (where they have input)
30	- Reads for: "What does this mean for my work? What decisions do I need to make?"
31	- Allergic to: Over-specified implementation, condescension, lack of technical depth
32	- Format: Context → What's being built → Technical unknowns → Asks
33
34	Design:
35	- Needs: User problem, user flows, principles (not implementation)
36	- Reads for: "What experience are we creating? What's the user's mental model?"
37	- Allergic to: Wireframe-level specs in PRDs, solutions disguised as requirements
38	- Format: User stories, flows, principles, open questions
39
40	Customer:
41	- Needs: "What's in it for me?" — tangible benefit in plain language
42	- Reads for: Understanding what changed and why it matters to them
43	- Allergic to: Internal jargon, process details, corporate hedging
44	- Format: Narrative — "you told us X, so we built Y, here's how to use it"
45
46	Board / Investors:
47	- Needs: Market context, competitive position, strategic rationale, progress vs. plan
48	- Reads for: "Is this team making good product bets?"
49	- Allergic to: Feature details, tactical minutiae, defensive framing
50	- Format: Insight → Strategic rationale → Progress → Next bet
51
52	Customer Success / Support:
53	- Needs: What changed, how to explain it, what questions users will ask, what to escalate
54	- Reads for: "How do I talk about this with customers?"
55	- Allergic to: Technical implementation details, strategic context they can't use
56	- Format: What shipped → User impact → FAQs → Edge cases to escalate
57
58	## Step 4 — Adapt the Content
59
60	For each target audience:
61	1. Identify the most relevant subset of the source content
62	2. Restructure the order to match the audience's reading priority
63	3. Rewrite for vocabulary and depth level appropriate to the audience
64	4. Add or remove context as needed
65	5. Reframe any feature statements as user benefit statements (for external audiences)
66
67	## Step 5 — Output
68
69	Produce the adapted version for each requested audience, clearly labeled. For each version, include a brief note on what was changed and why — this helps the user learn the tailoring principles for future communications.

People who liked this also viewed

6 picks

Type

audience-tailoring

70stars33forks

View on GitHub

How to install audience-tailoring?

productfculty-aipm/pm-copilot-by-product-faculty/audience-tailoring

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill audience-tailoring

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Audience Tailoring
2
3	You are adapting existing content for different audiences. The same underlying information needs to be structured, scoped, and toned differently depending on what the audience needs to do with it.
4
5	Framework: Pyramid Principle (structure matches audience's decision-making needs), Lenny's 14 PM habits (hunting for misalignment, clarity as core PM skill).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for stakeholder details — their roles, communication styles, sensitivities, and history. The more specific the memory, the more tailored the output.
10
11	## Step 2 — Understand the Source Content
12
13	Identify:
14	- What is the content being adapted? (PRD section, status update, decision memo, research synthesis?)
15	- What is the core message or decision the content contains?
16	- What is the source audience's level of technical or product context?
17
18	## Step 3 — Audience Analysis
19
20	For each target audience, establish:
21
22	Executive / C-level:
23	- Needs: Decision, risk, outcome — in that order
24	- Reads for: "What do I need to do or approve?"
25	- Allergic to: Details, jargon, long context, buried asks
26	- Format: Pyramid Principle — conclusion first, support second
27
28	Engineering / Technical team:
29	- Needs: Context (why), constraints (what not to do), decision points (where they have input)
30	- Reads for: "What does this mean for my work? What decisions do I need to make?"
31	- Allergic to: Over-specified implementation, condescension, lack of technical depth
32	- Format: Context → What's being built → Technical unknowns → Asks
33
34	Design:
35	- Needs: User problem, user flows, principles (not implementation)
36	- Reads for: "What experience are we creating? What's the user's mental model?"
37	- Allergic to: Wireframe-level specs in PRDs, solutions disguised as requirements
38	- Format: User stories, flows, principles, open questions
39
40	Customer:
41	- Needs: "What's in it for me?" — tangible benefit in plain language
42	- Reads for: Understanding what changed and why it matters to them
43	- Allergic to: Internal jargon, process details, corporate hedging
44	- Format: Narrative — "you told us X, so we built Y, here's how to use it"
45
46	Board / Investors:
47	- Needs: Market context, competitive position, strategic rationale, progress vs. plan
48	- Reads for: "Is this team making good product bets?"
49	- Allergic to: Feature details, tactical minutiae, defensive framing
50	- Format: Insight → Strategic rationale → Progress → Next bet
51
52	Customer Success / Support:
53	- Needs: What changed, how to explain it, what questions users will ask, what to escalate
54	- Reads for: "How do I talk about this with customers?"
55	- Allergic to: Technical implementation details, strategic context they can't use
56	- Format: What shipped → User impact → FAQs → Edge cases to escalate
57
58	## Step 4 — Adapt the Content
59
60	For each target audience:
61	1. Identify the most relevant subset of the source content
62	2. Restructure the order to match the audience's reading priority
63	3. Rewrite for vocabulary and depth level appropriate to the audience
64	4. Add or remove context as needed
65	5. Reframe any feature statements as user benefit statements (for external audiences)
66
67	## Step 5 — Output
68
69	Produce the adapted version for each requested audience, clearly labeled. For each version, include a brief note on what was changed and why — this helps the user learn the tailoring principles for future communications.

People who liked this also viewed

6 picks

Type