narrative-discover

To detect content opportunities, the workflow scans context from conversations, commits, and initiatives, then delegates analysis to a detector agent that surfaces signals with confidence scores. You receive structured detector output to evaluate.

The A/B/C judgment process is an adjudication step where you evaluate detected content opportunities and decide to immediately create content, register the idea as pending, or reject the signal entirely.

You can scope content discovery to a specific topic by running the workflow with the optional --topic flag. This filters the detector agent to surface only relevant signals and confidence scores for that subject.

Yes, you can extract content ideas from ongoing team initiatives. The workflow collects scan context from active conversations and initiatives, applying a detector-driven approach to identify valuable material opportunities.

The best way to register pending content ideas is to apply a B judgment during the A/B/C adjudication. This registers the detected opportunity into content records and project knowledge bases for future reuse.

Yes, narrative-discover operates without external dependencies. It uses an internal detector-driven workflow to scan context and output detector results for your A/B/C judgments directly.