feed-item-brief is a WordPress plugin that turns one feed item into a short summary draft for an editor. The source link, byline and publish time sit in an attribution block that the plugin renders itself. It is for sites that follow other publishers and want a summary in their own words that sends the reader to the original. Licence MIT. Version v0.1.0, released 19 November 2026.
It was written from scratch from an idea, as one of the utilities described on the engineering blog. It has not run on a live site.
Summarising other publishers’ items with a language model and a feed importer goes wrong in predictable ways.
The PRD adds a lesson about length. A model given only a range can run past the ceiling, and an instruction to count words can be printed back into the copy. Cutting long text is worse, because the last sentence often carries the attribution or the key date.
An item enters through feed_item_brief_submit or the batch hook. Intake validates it, cleans it and builds an article key, so mobile, AMP and tracking variants of one URL share a key. A second copy becomes a duplicate row. A changed body becomes an update note on the draft.
The item then waits in a table. WP-Cron runs every five minutes, newest first, five items and twenty seconds per run, and each item is leased so overlapping runs never take it twice. Classifier decides what the item is. Gate then checks the switch, an auth pause and the daily cap before a call. Summariser makes one call with a JSON schema through llm-json-php, or through a filter you supply. OutputChecker examines the result. Drafter inserts the post.
The output checks run in code. Self-narration lines are removed. Every number, and every quote of four words or more, must appear in the source. Phrases that imply several sources fail. Over-length text fails and is never cut. The wrong language fails. A failure gets one retry with the reasons named, and a second failure ends as check_failed. Relative time words are flagged for the editor, not rejected.
The attribution block is dynamic: readers see it rendered from post meta, and its saved markup is a static fallback that survives if the plugin is removed. Data lives in two tables, {prefix}feed_item_brief_items and {prefix}feed_item_brief_daily, plus post meta.
A call from your own importer looks like this:
do_action('feed_item_brief_submit', [
'url' => $link,
'title' => $title,
'body' => $html,
'source_name' => 'Example News',
'byline' => ['Jane Roe'],
'published' => '2026-11-14T09:00:00Z',
'guid' => $id,
], 'my-importer');
The call records the item and returns at once. No model call, page fetch or post insert happens in the importer’s request.
_doing_it_wrong() notice.FEED_ITEM_BRIEF_DISABLED, wins over the setting, and the switch is read at the moment of every model call.nosnippet or noarchive become link-only drafts.An independent review of the build PR found and fixed these before the merge.
spend_meter_pre_spend filter with a full intent array, allows a call only on an explicit yes, and reports the outcome through an action.news.example.co.uk and example.co.uk count as different sites.time element in the first article. It is not an extraction engine.No issues are open on the repo. Test status: this is v0.1.0. There are 136 PHPUnit tests with 698 assertions, and they pass, including six database tests on a throwaway MySQL 8.0, and PHPStan level 8 and phpcs are clean. The tests use stubs and mocks. The CI workflow has not run on GitHub, and there is no production mileage.
It needs WordPress 6.4 or later and PHP 8.1 or later, with the dom, json and mbstring extensions. Neither package is on Packagist yet, so both are VCS repositories.
composer config repositories.feed-item-brief vcs https://github.com/IndianOpinion/feed-item-brief
composer config repositories.llm-json-php vcs https://github.com/IndianOpinion/llm-json-php
composer require indianopinion/feed-item-brief