Background
The backlog-suggester agent is currently invoked manually via /suggest-content. A natural improvement is to trigger it automatically after /write-content completes — surfacing content gaps while the article is still in context.
More broadly, this pattern applies to other agents too: fact-checker after drafting, content-linker after writing, style-enforcer as a post-write gate, etc.
What to build
A hook-based auto-trigger system for content-ops agents, configurable per-project:
- Define triggers in
.content-ops/config.md (e.g. on_write_complete: [backlog-suggester, fact-check])
- Implement as a
PostToolUse or Stop hook that reads the config and dispatches the right agents
- The
/init backlog-suggester round (and future agent rounds) should ask during setup whether auto-triggering is desired
Scope
Notes
The auto-trigger claim was removed from the /init backlog-suggester confirmation message until this is actually implemented.
Background
The
backlog-suggesteragent is currently invoked manually via/suggest-content. A natural improvement is to trigger it automatically after/write-contentcompletes — surfacing content gaps while the article is still in context.More broadly, this pattern applies to other agents too: fact-checker after drafting, content-linker after writing, style-enforcer as a post-write gate, etc.
What to build
A hook-based auto-trigger system for content-ops agents, configurable per-project:
.content-ops/config.md(e.g.on_write_complete: [backlog-suggester, fact-check])PostToolUseorStophook that reads the config and dispatches the right agents/init backlog-suggesterround (and future agent rounds) should ask during setup whether auto-triggering is desiredScope
/init backlog-suggesterto configure auto-trigger opt-inNotes
The auto-trigger claim was removed from the
/init backlog-suggesterconfirmation message until this is actually implemented.