gsd-ns-ideate

Route user intent to exploration or capture workflows for ideation outputs.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-ns-ideate-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ns-ideate
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-ns-ideate
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-ns-ideate-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly turn an intent into the correct lightweight exploration or documentation action, so your thinking becomes reusable outputs like sketches, spikes, specs, and captured backlog items.

Core Features & Use Cases

  • Intent-based Skill routing: Chooses the appropriate exploration/capture Skill for what you want to do next.
  • Idea-to-artifact capture: Supports exploring, sketching, time-boxed spikes, and writing specs for a phase.
  • Unified capture for planning artifacts: Captures a thought as a todo, note, backlog item, or seed (and can list pending todos).

Quick Start

Use the slash command to route your intent, for example: openforce /code-review to trigger the appropriate action that matches your request.

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 to the right exploration or capture workflow?

Intent routing matches your request to the appropriate ideation mode, selecting parameters to invoke the correct skill for capturing notes, sketches, spikes, or phase specs. This ensures thoughts become reusable planning artifacts.

What is the best way to turn a technical spike idea into a captured backlog item?

Capturing a backlog item from a technical spike uses intent-based skill routing to time-box the investigation and transform thoughts directly into structured planning artifacts like todos or seeds.

Can I use intent routing to draft a phase spec from unstructured notes?

Drafting a phase spec from unstructured notes is supported by routing your intent to the appropriate spec drafting mode. This transforms raw ideation outputs into unified planning artifacts.

Does this approach require predefined parameters to capture todos and backlog items?

Capturing todos and backlog items requires no manual parameter setup, as the intent routing mechanism automatically matches your request and selects the correct skill mode to list or store pending items.

When should I use intent routing instead of manually organizing ideation outputs?

Use intent routing when you need to quickly turn unstructured thoughts into lightweight exploration actions like sketches or specs, rather than manually sorting notes, spikes, and backlog items.

Why use an intent router for ideation and spec drafting instead of standard note-taking tools?

An intent router for ideation dynamically directs requests to specialized capture workflows for spikes and specs, whereas standard note-taking tools lack automated routing to generate structured planning artifacts.