gsd-ns-ideate

Route user intent into exploration, sketching, spike, spec, or capture workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns an ambiguous “I have an idea” or “help me plan this” moment into the right exploration or capture workflow, so thoughts don’t get lost and follow-ups become actionable.

Core Features & Use Cases

  • Intent-based routing: Selects the correct follow-up action from exploration, sketching, time-boxed spikes, spec capture, or general capture.
  • Structured output targets: Guides the user to the appropriate capture destination, including pending todos via list mode.
  • Unified capture modes: Supports capturing notes, backlogs, and seed ideas through a single capture skill using mode flags.

Example: When you want to validate uncertainty, you can run a time-boxed spike; when you want alignment, you can capture a phase spec; when you just need to get it out of your head, you can capture a note/backlog/seed.

Quick Start

Tell the Skill what you want to do, such as “Sketch a rough design for the new onboarding flow,” to invoke the matching exploration or capture step.

Frequently Asked Questions about gsd-ns-ideate

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

FAQPage Schema
How do I route an idea into the right backlog or exploration workflow?

Idea routing matches your raw intent to the correct workflow, sending thoughts to exploration, sketches, technical spikes, or phase specs. This prevents ideas from getting lost and turns ambiguous planning moments into structured, actionable artifacts.

What is the best way to capture a quick product idea or pending todo?

Quick idea capture uses unified capture modes for notes, backlogs, and seeds. You can route your intent directly to a general capture workflow or a list mode to immediately record pending todos, ensuring raw thoughts become structured follow-ups.

How do I plan a technical spike to validate engineering uncertainty?

Planning a technical spike involves routing your intent to a time-boxed spike workflow. This structured exploration action helps validate uncertainty during product and engineering planning by quickly moving from a raw thought into an actionable spike artifact.

When do I need to capture a phase spec instead of a general backlog item?

Capturing a phase spec is needed when you want team alignment on a planned initiative. Intent routing directs your thought to the spec-phase workflow when your goal requires structured phase definition rather than just adding a general backlog item or note.

Can I sketch a rough design for a new feature flow?

Sketching a rough design is supported by routing your intent to the sketch workflow. This applies to product and engineering planning scenarios, allowing you to quickly generate structured sketches from raw thoughts to visualize your ideas.

Does idea routing require any specific technical dependencies?

Idea routing requires no specific technical dependencies to function. It relies solely on matching your stated intent to the correct invocation for exploration, capture, or phase spec generation, making it immediately accessible for planning scenarios.