intake

To capture story ideas into a backlog without the heavyweight pipeline overhead, use a lightweight workflow that extracts intent, populates a stub template, and records an index entry. This preserves conversational context directly as a backlog item without triggering analysis or research.

The best way to save conversation context as a backlog stub is to use a lightweight capture workflow that writes a stub file and adds an index entry via momentum-tools. This enforces the item remains in backlog status and avoids heavyweight development gates.

Capturing a story backlog stub does not require subagents or analysis. The workflow performs lightweight capture by extracting conversational intent, writing the stub, and recording an index entry while explicitly avoiding subagents, research, and heavyweight analysis.

To create an index entry for a new story backlog item, the capture workflow uses momentum-tools to add the entry. This surfaces the stub in the backlog while minimizing tool calls and avoiding the full create-story development gates.

Use a lightweight story capture workflow instead of a full create-story pipeline when you need to quickly preserve why and what from an ongoing conversation. It avoids heavyweight analysis and research overhead, enforcing the item stays a backlog stub until you are ready for full development.