intake

Capture conversation story ideas into backlog stub files with index entries.

Updated Mar 10, 2026

Search Tags:#workflow #momentum #intake #stub #index-entry #story-backlog

Ready to run

npx skills add https://github.com/iamsteveholmes/momentum --skill intake-iamsteveholmes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/intake
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill intake-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Capture ideas and context from ongoing conversations and convert them into backlog stub entries, avoiding the overhead of running a full create-story pipeline.

Core Features & Use Cases

Lightweight story capture from conversation.
Write a backlog stub file with minimal context, preserving why and what.
Write an index entry via momentum-tools to surface the stub in the backlog.
No analysis, no subagents required.

Quick Start

Invoke the intake workflow to capture the latest conversation into a backlog stub using momentum.

Frequently Asked Questions about intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture story ideas from a conversation into a backlog without running a full create-story pipeline?▼

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.

What is the best way to save conversation context as a backlog stub file?▼

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.

Does capturing a story backlog stub require subagents or analysis?▼

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.

How do I create an index entry for a new story backlog item?▼

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.

When should I use a lightweight story capture workflow instead of a full create-story pipeline?▼

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.