Expand targeting without wrecking CPA — lookalike ladders, seed quality, audience layering, and exclusion hygiene across platforms. Use when a user wants to scale beyond exhausted audiences, build lookalikes, fix audience fatigue, or set up exclusion lists.

Audit a Google Ads account's structure — ad group focus, keyword duplication, match-type distribution, cross-campaign conflicts, and naming consistency. Use when a user wants an account audit, asks why an account is hard to manage, or suspects duplicate keywords or messy structure.

Research competitors' advertising — the creative they run, their angles and offers, and where they compete for the same auctions. Use when a user wants competitive research, creative inspiration, to see what rivals are running, or market positioning for ads.

Connect ad accounts and GA4 through the Synter browser flow and verify the selected workspace.

Verify available conversion and pixel diagnostics before launch; hand off tag changes to the account owner.

Diagnose creative fatigue; refresh cadence; when to swap/rotate ads; frequency caps; CTR drop / CPM rise signals; per-platform creative lifespans.

Analyze hour-of-day and day-of-week performance and set ad schedules and bid modifiers to spend when conversions happen. Use when a user wants to optimize ad scheduling, set dayparting, find the best times to run ads, or cut spend during dead hours.

Build C-suite and board ad reports — blended ROAS, month-over-month and year-over-year, pacing, and a plain-English narrative of what happened and what to do. Use when a user wants an executive summary, a board report, or a monthly performance review across platforms.

Build a post-cookie first-party data strategy — Enhanced Conversions, server-side tracking, Consent Mode v2, and planning how to use owned data for targeting. Use when a user wants to recover lost conversion data, set up Enhanced Conversions or CAPI, implement consent mode, or plan for cookie deprecation.

Check intended geography against available campaign settings and delivery evidence; identify unverified targeting before launch.

Explain the bundled skills, supported MCP tools, OAuth setup, and support options.

Prepare landing-page copy and an implementation brief using the advertiser's verified brand, offer, and conversion destination. This directory package does not publish websites.

Build LinkedIn Ads audiences with job title, seniority, and company targeting, ABM company lists, lookalikes, and lead gen form optimization. Use when building LinkedIn audiences, setting up ABM, choosing ad formats, optimizing lead gen forms, or estimating LinkedIn costs.

Assess brand discoverability using supplied AI-search results, website content, and crawl evidence. Distinguish observed citations from untested recommendations.

Build a full media plan — objective, channel mix, budget split, projected CPM/CPC/CPA, and a first test flight — before any campaign is built. Use when a user wants a media plan, a budget allocation across platforms, or a go-to-market for a launch.

Mine and manage negative keywords from search-term reports to stop wasted spend, and detect match-type bleed and cross-campaign conflicts. Use when a user wants to cut wasted spend, clean up search terms, build negative lists, or fix irrelevant clicks on Google or Microsoft Ads.

Triage and answer replies to cold email campaigns in Synter Outbound — separate real humans from auto-responders, classify intent, draft a reply in the sender's voice, and route opt-outs to suppression. Use when a user asks about outbound replies, their unibox, who responded to a campaign, or wants to answer a prospect.

Discover and qualify prospects in Synter before writing cold outreach — find people and verified contact info (emails, phone numbers, LinkedIn URLs), verify a checkable fact from first-party signals, rank competing signals, and land it in the email without sounding AI-generated. Use when finding prospects or leads, building or topping up an outbound list or lead list, writing a first-touch cold email to a researched prospect, or deciding whether someone should be contacted at all.

Find prospects (verified emails, phone numbers, LinkedIn URLs) and run cold email outbound through Synter Outbound — search contacts, enrich identifiers, review the pipeline, inspect campaigns, check sending health, and pause or resume. Use when a user asks to find prospects, emails, phone numbers, LinkedIn profiles, or asks about outbound, cold email, sequences, their lead pipeline, reply rates, or wants to launch, pause, or top up an email campaign.

Audit client-side pixels and server-side Conversions API implementations across Meta, Google, TikTok, LinkedIn, Reddit, and Microsoft — setup, Event Match Quality, deduplication, and click-ID capture. Use when conversion counts disagree between platforms, EMQ or match rates are low, or tracking needs verification before scaling spend.

Ground channel-mix and budget-split decisions in typical CPM, CPC, and CPA ranges per platform, and set realistic performance expectations. Use when a user asks what to expect on a platform, how to split budget across channels, or whether their numbers are normal.

Sign in through OAuth, confirm the workspace, and run a first report or campaign plan.

Build a cross-channel performance report — spend, conversions, CPA/ROAS, attribution, and an executive narrative. Use when a user asks how campaigns are doing, wants a weekly/monthly report, a board/exec summary, or to reconcile numbers across platforms.

Calculate ROAS, CPA, break-even, max CPC, and campaign profitability from real spend and revenue, and set realistic targets. Use when a user asks whether a campaign is profitable, what ROAS or CPA they need, what to bid, or wants the unit economics behind ad spend.

Write creator briefs with verified brand context, hooks, shot lists, claims, deliverables, and usage-rights requirements. Use when planning creator-style ads.

Build consistent, correctly structured UTM parameters for ad URLs so traffic shows up cleanly in analytics. Use when a user needs UTM tags, tracking URLs, campaign links, or their analytics source/medium data is a mess.

Write platform-specific video ad scripts with second-by-second timing marks — YouTube bumpers and pre-roll, TikTok native, Reels, and 30s narrative ads. Use when writing video scripts, storyboarding an ad, improving hook rates, or briefing video generation.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Reviews the entire PLAN.md of a new project through fixed, file-only provider rounds. Triggered by plan-mode when every plan entry is draft; Round 1 alternates Codex and Claude, then returns control to a human checkpoint.

Builds and maintains openspec/PLAN.md, the human-approved plan that sequences OpenSpec changes toward a stated goal — the tier above tasks.md. Explore read-only, draft entries, then stop and ask for approval; a change cannot start until its entry is approved. Trigger — make a plan, what should we build first, plan the work, roadmap, add this to the plan, approve the plan, why is the plan gate failing, NO-ENTRY, HASH-MISMATCH.

Rewrites a confirmed REFINED_PROMPT.md from prompt-loop into an ENGINEERED_PROMPT.md ready to execute: cleaned of reasoning-scripting and shouting, structured into the task contract (objective, context, scope, tools, action boundaries, verification, output, stop condition), every change traced to a numbered prompting rule, the lock register carried byte-identical, and an effort level recommended. Runs in a fresh-context subagent and never asks the user anything. Trigger — automatically after prompt-loop's output contract is confirmed and before openspec-propose, for non-trivial development work; explicitly on: engineer this prompt, ottimizza il prompt, prompt engineering, ingegnerizza il prompt, make this prompt executable. Do not use it on a prompt that has not been through prompt-loop: without a confirmed REFINED_PROMPT.md there is nothing to engineer.

Refines an incoming prompt through a bounded score → interview → lock → rewrite loop until it is mechanically good enough (rubric score ≥ 9/10) to feed the SDD workflow. Trigger — automatically before openspec-propose when the request is non-trivial development work; explicitly on: refine this prompt, prompt loop, score my prompt, is this prompt ready.

Structured interview process that turns a vague stakeholder request into clear, actionable requirements before any spec or code is written. Trigger — new feature request, unclear requirements, vague task, clarify scope, before proposing a change.

Single entry point to the spec-as-source workflow: given a request, decides which of the plugin's skills to activate — excluding trivial work first, deriving the current phase from the state of the repo second, and matching descriptions last — then runs the chosen skill inline or in a subagent. Use when you do not know which skill applies, or want the workflow driven for you. Trigger — which skill should I use, what do I do next, route this, start working on X, implement X, propose a change, continue the implementation, I want to build X, help me with this project, non so da dove partire.

Installs the spec-as-source OpenSpec schema, enforcement scripts, CI workflow, and pre-commit hooks into a project. Trigger — setup spec enforcement, add spec checks, configure spec-as-source, install spec scripts, add spec CI, install openspec schema.

Syncs .github/workflows/spec-verification.yml with the test runner and test files declared in specs. Trigger — update CI workflow, sync spec CI, regenerate workflow, CI out of sync with specs, add spec test to CI.

Runs an autonomous Ralph-style loop over the tasks of an active OpenSpec change: one task per fresh-context agent invocation, mechanically gated by scripts/verify.sh, with runaway guardrails. Trigger — run the loop, ralph loop, autonomous apply, loop the tasks, implement the change unattended.

Deletes all files declared as targets in openspec/specs/**/spec.md and rebuilds them from the specs to verify spec-as-source integrity. Trigger — clean rebuild, verify source of truth, spec drift check, regenerate from specifications, rebuild from spec.

Runs all spec consistency checks (link integrity, target ownership, manifest build), the test suite, and a semantic drift spot-check, then reports results. Trigger — verify specs, spec check, run spec suite, check spec consistency, validate spec links, spec integrity, spec drift.

Creates and maintains capability spec.md files under openspec/specs/: requirements, scenarios, targets frontmatter, and Verified by test links. Trigger — write a spec, update a spec, document requirements, create capability spec, spec drift in frontmatter or links.

Reviews completed implementation requirement-by-requirement against its capability spec, with file:line evidence, before declaring work done. Trigger — review my work, is this done, verify completeness, check against spec before merging, final review.