gsd-capture

Route captured ideas into GSD todos, notes, backlog, or seed plans.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-capture-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-capture
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-capture
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-capture-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents important thoughts, tasks, and future ideas from getting lost by routing every capture into the correct GSD destination workflow.

Core Features & Use Cases

  • Mode-based capture routing: Sends your input to structured todos, timestamped notes, backlog items, or seed plans based on flags like --note, --backlog, --seed, and --list.
  • Todo and backlog organization: Maintains a consistent destination structure such as .planning/todos/ and ROADMAP.md backlog (999.x numbering) so work stays searchable and actionable.
  • Interactive selection: Provides a list mode to browse pending todos and route an appropriate follow-up action.

Quick Start

Run gsd-capture with your text to add a structured todo for later work.

Frequently Asked Questions about gsd-capture

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

FAQPage Schema
How do I capture tasks and notes into a structured productivity backlog?

You can capture tasks and notes into a structured productivity backlog by routing inputs via command flags. The system parses the leading flag from your arguments and dispatches the text to the corresponding workflow, preserving workflow gates while executing the capture.

What is the best way to route ideas into todos, notes, and seed plans?

Routing ideas into todos, notes, and seed plans is handled through mode-based capture routing. By using flags like --note, --backlog, and --seed, the system sends your input to structured todos, timestamped notes, or forward-looking seed plans.

How do I organize my backlog items and todos so they stay searchable?

To organize backlog items and todos so they stay searchable, the system maintains a consistent destination structure such as a .planning/todos/ directory and a ROADMAP.md backlog using 999.x numbering. This ensures work remains actionable and easy to find.

Can I browse pending todos and select a follow-up action interactively?

Yes, you can browse pending todos and select a follow-up action interactively. The system provides a list mode, activated with the --list flag, to display pending todos and route an appropriate follow-up action directly.

Do I need any external dependencies to use this capture workflow routing?

No external dependencies are required to use this capture workflow routing. The system operates independently to parse arguments, apply command flags, and dispatch inputs into todos, notes, backlog items, or seed plans.

When should I use seed planning instead of adding a regular todo?

You should use seed planning instead of adding a regular todo when you have forward-looking ideas that are not immediately actionable. Using the --seed flag routes the input to a seed plan, keeping it separate from immediate structured todos.