Answer-first rewrite of the PLG metrics post
VerifiedreadExecutes now · no side effectsprompt-executorheading restructure · impact 69 · effort M · updated 12d ago
The change
This executor renders a prompt rather than a patch — it does not touch your repo at all.
Self-contained: the issue, the change, file patterns for App Router, Pages Router and static layouts, and the acceptance checks restated as things to verify. Paste it into any coding agent.
Rewrite the opening of /blog/plg-metrics so the definition of activation rate is the first sentence. Keep the existing narrative opening, moved below a "Why this metric drifts" heading.
Why this fix
The evidence behind the recommendation, and what it is expected to move.
Removes 90 words of throat-clearing before the claim.
- First substantive sentence at word 94
Acceptance checks
How any of the three executors proves it worked. Identical for all of them.
- first_words_containActivation rate is
- audit_issue_resolvediss_009
Verification
Re-measured at T+3d and T+14d against position.
7d before / T+14d after · measured 31 Jul 06:00 UTC
Task
- Task id
ft_07- Kind
- heading_restructure
- Executor
- prompt-executor
- Band
- read
- Target
- acme.com/blog/plg-metrics
- Anchor
- after_h1
- Repo
- not used
- Requested by
- Daniel Okoro
- Channel
- DASHBOARD
- Created
- 12 Jul 06:00 UTC
File targets
How the executor finds this page in a repo it has never seen.
App Router
- content/blog/plg-metrics.mdx
Pages Router
- pages/blog/plg-metrics.tsx
Static
- blog/plg-metrics.html