From comms-strategy
This skill should be used when the user asks to 'organize agency files', 'set up PARA', 'structure my workspace', 'organize my briefs and campaigns', 'triage my inbox', or 'clean up my data folder'.
npx claudepluginhub jamon8888/cc-suite --plugin Comms StrategyThis skill uses the workspace's default tool permissions.
Organizes the `data/` folder using PARA methodology, adapted for a brand and communications agency. Maintains clean separation between active client work, ongoing agency responsibilities, reference material, and completed projects.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Organizes the data/ folder using PARA methodology, adapted for a brand and communications agency. Maintains clean separation between active client work, ongoing agency responsibilities, reference material, and completed projects.
data/
├── 0-Inbox/ # New briefs, assets, requests awaiting triage
├── 1-Projets/ # Active work with live deadlines
│ ├── clients/ # [ClientName].md — profile, history, contacts
│ ├── briefs/ # brief-[client]-[YYYY-MM].md
│ ├── campaigns/ # [campaign-name]/ — strategy, assets, reports
│ ├── pitches/ # [prospect]-pitch-[YYYY-MM].md
│ └── frameworks/ # Agency methodologies in active use
├── 2-Domaines/ # Ongoing agency responsibilities (no deadline)
│ ├── agency-profile.md # Agency identity — single source of truth
│ ├── media-contacts/ # Journalist, editor, influencer relationships
│ └── voice-guidelines/ # Brand voice standards and tone guides
├── 3-Ressources/ # Reference material — permanent
│ ├── templates/ # Brief, platform, campaign templates
│ ├── case-studies/ # Past campaigns kept as reference
│ └── research/ # Sector intelligence, audience data
└── 4-Archives/ # Completed or inactive items
├── campaigns/ # Signed-off campaigns
└── pitches/ # Closed pitches — prefix won- or lost-
Format: [YYYY-MM]_[TYPE]_[client-or-topic].[ext]
| Code | Category | Example |
|---|---|---|
BRIEF | Active brief | 2026-02_BRIEF_renault-repositioning.md |
STRAT | Comms strategy / platform | 2026-02_STRAT_renault-comms-platform.md |
CAMP | Campaign document | 2026-02_CAMP_renault-spring-launch.md |
PITCH | New business pitch | 2026-02_PITCH_sncf-brand-refresh.md |
AUD | Audience analysis | 2026-02_AUD_renault-gen-z-segment.md |
MEAS | Measurement framework | 2026-02_MEAS_renault-q1-kpis.md |
REF | Reference / research | 2026-01_REF_automotive-sector-study.md |
Read data/ structure. Report:
0-Inbox/ (need triage)Create any missing directories. Offer to create placeholder README.md files in empty folders so structure is visible.
Do not create directories that already exist. Confirm scaffold plan before executing.
For each file in 0-Inbox/, ask:
1-Projets/2-Domaines/3-Ressources/4-Archives/Move and rename files per convention. User approval required before any move or rename.
Log each operation:
[YYYY-MM-DD HH:MM] MOVED: 0-Inbox/brief.md → 1-Projets/briefs/2026-02_BRIEF_acme-rebrand.md
Move a campaign to 4-Archives/campaigns/ when:
Move a pitch to 4-Archives/pitches/ when won or lost. Use prefix won- or lost- for easy filtering.
Process 0-Inbox/ in under 5 minutes:
1-Projets/2-Domaines/3-Ressources/4-Archives/If interrupted, resume by:
0-Inbox/ for remaining untriaged items