feat(content-ops): auto-trigger backlog-suggester (and other agents) via hooks after key operations

[pcamarajr]

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

• Design the config schema for agent triggers
• Implement the hook dispatcher
• Update /init backlog-suggester to configure auto-trigger opt-in
• Document which agents are safe to auto-trigger and which should stay manual

Notes

The auto-trigger claim was removed from the /init backlog-suggester confirmation message until this is actually implemented.