docs/social_branding/prd-additions.md

PRD additions we can implement next (excluding posting + new platforms)

Date: 2026-03-26
Source: docs/PRD.md
Exclusions: (1) anything that actually posts/executes content to platforms, (2) adding/supporting new platforms beyond the current LinkedIn-first implementation.

This doc lists only items explicitly described in the PRD that are either missing or only partially implemented in the current codebase.

---

1) Brand Score: full PRD component model + breakdown

PRD section: “2.1 Brand Score Components”, “2.2 Brand Score → RQx Integration”

Add the remaining Brand Score components as first-class computed fields (and store their breakdown), not just a profile audit-derived score:

• Content Consistency (20%): consistency of posting frequency + tone consistency over a rolling window.
• Audience Growth (15%): follower/connection growth rate over a 30-day rolling window.
• Engagement Rate (15%): likes/comments/shares/saves as % of reach.
• Recruiter Visibility (15%): profile appearance rate in recruiter/talent searches (LinkedIn primary).
• Content Quality (10%): AI-assessed relevance/originality/alignment to persona framework.
• Cross-Platform Consistency (5%): messaging/voice alignment across connected platforms (schema-ready; compute from available platforms only).

Also implement PRD-required outputs:

• Brand Score trend line (history storage + API response)
• “objective, measurable signals” explanations per component

---

2) Brand Score → RQx mapping + events

PRD section: “2.2 Brand Score → RQx Integration”

Implement/confirm the PRD mapping and event rules end-to-end:

• Compute & store RQx contribution as: Brand Score × 0.4
• Ensure recalculation runs after every platform sync (LinkedIn daily in PRD)
• Emit update when Brand Score changes by 5+ points (PRD) and include before/after + metadata
• Persist and expose Brand Score history for the dashboard (trendline)

---

3) LinkedIn profile rewrite variants + user selection

PRD section: “5.1 LinkedIn → Profile Rewrite”

Generate PRD-specified rewrite options for user approval/selection:

• Headline: 3 variants
• About section: optimized version(s)
• Experience bullet points (per role)
• Skills list mapped to Q-Scores + target JD keywords

This is PRD “Generate → Approve” behavior and does not require posting.

---

4) Recruiter visibility: keyword gap analysis + injection recommendations

PRD section: “5.1 LinkedIn → Recruiter Visibility”; Brand Score component “Recruiter Visibility”

Add the PRD keyword gap workflow:

• Identify missing recruiter-search terms for the target role
• Provide where to inject them (headline/about/experience/skills) and generate suggested rewrites
• Score each section 0–100 and benchmark vs target role (PRD says “benchmark against top 10% in same role”)

---

5) Connection strategy drafts (no sending)

PRD section: “5.1 LinkedIn → Connection Strategy”

Implement the PRD deliverables without executing any connection actions:

• Identify target connections (target companies, peers, hiring managers)
• Draft personalized connection request notes for approval
• Track acceptance-rate analytics inputs (data collection method TBD per PRD)

---

6) Engagement response drafts (approval-gated, no automation)

PRD sections: Pillar “Engagement”; “4.2 Dynamic Content → Engagement response drafts”; “5.1 LinkedIn → Engagement Automation”

Add draft generation (only) for:

• Replies to comments on user posts
• Comments on posts from target connections/industry leaders

All actions remain draft-only and approval-gated.

---

7) Content calendar generation rules enforcement (planning-side only)

PRD section: “4.3 Content Calendar Generation Rules”

Enforce the PRD rules in calendar generation + approval queue mechanics:

• Rule 1: Frequency enforcement + reminders 48hrs in advance if slots aren’t approved
• Rule 2: Platform sequencing (formatting/unique versions) — for now enforce at least “no naive duplication” within LinkedIn content types/templates
• Rule 3: 80/20 split maintained over a rolling 2-week window
• Rule 4: No auto-post without approval (keep; optionally support PRD “auto-approve mode” as opt-in approval behavior, not posting)
• Rule 5: Tone lock after first 2 weeks unless user resets
• Rule 6: Sensitive topic filter: risky content is flagged and not queued for approval

These changes are about planning, generation, and approvals, not posting.

---

8) Tracking + weekly analytics dashboard (read-only metrics)

PRD section: “1.1 The Automation Loop → Track”; “5.1 LinkedIn → Analytics Tracked”

Implement the PRD “Track” layer to collect, store, and display (no posting needed):

• Profile views (7-day, 30-day)
• Search appearances
• Post impressions
• Engagement rate per post
• Connection acceptance rate
• Follower growth

Add PRD-required presentation:

• Weekly analytics dashboard
• Brand Score trend line

---

9) Data requirements layer (LinkedIn) — collection mechanism + constraints doc

PRD section: “6. Data Requirements — Individual”

PRD leaves the method “TBD by technical team” but requires confirmation of availability. Add the engineering artifacts the PRD calls for:

• Document collection mechanism (API vs scraping vs user export)
• Document legal/rate-limit constraints
• Confirm which fields in PRD can/can’t be reliably collected now
• Implement a stable “profile snapshot + metrics snapshot” storage model for the required data

---

10) Persona switching support

PRD section: “3. Six end-goal personas — content framework”

PRD states users can switch personas as goals evolve. Implement:

• Changing persona for a profile
• Persist persona choice and regenerate future calendar/drafts under the new persona
• Keep approval queue consistent (what happens to existing suggested/scheduled items)

---

Notes / alignment with current repo state

• The repo already has foundations for: LinkedIn profile ingest, audit, deterministic calendar/draft generation, approval workflow, Brand Score v1, and dashboard state.
• The items above are the next PRD-scoped additions that don’t require new platforms or posting.