Use when someone wants a guide or report and twenty published posts already cover most of it.
gated-asset-from-published-posts.md
You are planning a long asset assembled from published posts. You are not writing it and you are not stitching the posts together in publication order.
Published posts with title, summary and main sections: {{PUBLISHED_POSTS}}
What the asset is and who downloads it: {{ASSET_AND_AUDIENCE}}
What the reader should be able to do afterwards: {{READER_CAPABILITY}}
Length and effort we can afford: {{PRODUCTION_BUDGET}}
Output:
1. Chapter plan table: Chapter | What it delivers towards {{READER_CAPABILITY}} | Source posts from {{PUBLISHED_POSTS}} | Reuse level (as is, edit, rewrite, new) | Approximate length.
2. Overlap resolution: where two posts cover the same ground, which version survives and what the other one contributes.
3. Gaps: chapters with no source at all, each with what has to be created and who can create it.
4. What this offers a reader in {{ASSET_AND_AUDIENCE}} beyond reading the posts for free. If the honest answer is only convenience, say so plainly.
5. What happens to the source posts afterwards: keep, link to the asset, or trim.
Rules:
- Do not plan chapters {{PRODUCTION_BUDGET}} cannot cover. Cut to fit and list what was dropped.
- Do not carry a claim into the asset that its source post did not support.
- Order chapters by the reader's sequence of questions, not by when the posts were published.
- No em dashes. British spelling.
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
When should I plan the asset rather than start assembling it?
Before anyone commits to a date. Stitching posts together in publication order is the obvious move and produces a download nobody finishes. This plans chapters by the sequence of questions a reader has, and names the sections that have never been written, which is what the schedule actually depends on.
What do I need to gather before planning it?
The published posts with titles, summaries and main sections, what the asset is and who downloads it, what the reader should be able to do afterwards, and the length and effort you can afford. The budget forces the cuts, and it lists what was dropped rather than planning past your capacity.
What does the plan cover?
A chapter plan mapping source posts with a reuse level and length, overlap resolutions, gaps with who has to fill them, an honest answer on what the asset offers beyond the free posts, and what happens to the source posts. Run it before anyone starts designing a cover.
What blows the timeline?
Reading the reuse column as an effort ranking. A chapter marked rewrite can cost more than one marked new, so check it against real writing time before you commit. If section 4 comes back saying convenience only, that is a legitimate answer, but scale the design spend to match it.