quick-capture

Route raw ideas to bounded contexts and create backlog tasks.

27|6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/heimeshoff/Agentheim --skill quick-capture-heimeshoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-capture
Source: https://github.com/heimeshoff/Agentheim/tree/main/skills/quick-capture
Command: npx skills add https://github.com/heimeshoff/Agentheim --skill quick-capture-heimeshoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick-capture enables users to offload ideas, bugs, or features into the backlog without conversation or refinement, keeping momentum and preventing context-switching.

Core Features & Use Cases

  • Fast backlog entry: converts raw ideas into backlog tasks with minimal friction.
  • BC routing: routes each idea to the best-fit bounded context for proper ownership.
  • One-task-per-idea: writes a separate backlog task per idea and logs routing clearly.
  • Index & protocol integration: updates the BC INDEX and records a protocol capture for traceability.

Quick Start

Speak the trigger phrases and the idea, and the skill will route it to the best BC and create a backlog task.

Frequently Asked Questions about quick-capture

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

FAQPage Schema
How do I quickly capture ideas into a backlog without interrupting my workflow?

Quick-capture routes raw ideas to the best-fit bounded context and creates a backlog task for each. It handles multiple ideas simultaneously, updates the target BC INDEX, and logs a protocol capture per task without asking clarifying questions.

How does routing ideas to a bounded context work for task management?

Routing ideas to a bounded context works by analyzing each raw idea and directing it to the best-fit domain area. It then updates the BC INDEX and logs a protocol capture per task to ensure full traceability of the newly created backlog entries.

Can I log multiple ideas at once and still get a separate backlog task per idea?

Yes, you can log multiple ideas at once and still receive a separate backlog task per idea. The system processes each raw capture individually, routing it to the best-fit bounded context and writing a distinct backlog entry without requiring manual edits.

Do I need to manually edit or refine raw captures before they enter the backlog?

No, you do not need to manually edit or refine raw captures before they enter the backlog. The process requires no clarifying questions, ensuring raw captures are immediately routed to a bounded context and made ready for later refinement.

What is the best way to prevent context-switching when logging new features or bugs?

The best way to prevent context-switching when logging new features or bugs is to use an automated routing system that offloads raw ideas directly into the backlog. This maintains momentum by skipping conversation and refinement phases entirely.

Why does my backlog task routing need a protocol capture log?

A backlog task routing protocol capture log is needed to maintain traceability for each newly created entry. It records the routing action alongside updating the bounded context INDEX, ensuring the origin and destination of raw captures are tracked.