idea

Analyze natural language feature requests against project codebases and generate JSON issue specifications.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill idea-hiddink-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/idea
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill idea-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between vague natural language concepts and actionable development tasks by automatically analyzing feasibility and generating structured issue specifications.

Core Features & Use Cases

  • Feasibility Assessment: Evaluates the scope, complexity, and potential risks of a proposed feature against the existing codebase.
  • Structured Output: Generates ready-to-use JSON issue specifications including titles, descriptions, and labels.
  • Use Case: When a team member suggests a new feature like adding OAuth support, this skill analyzes the current project structure to identify affected modules and creates a detailed implementation plan.

Quick Start

Invoke the idea skill followed by your feature request to receive a structured analysis and issue specification.

Frequently Asked Questions about idea

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

FAQPage Schema
How do I assess technical feasibility for a feature request against an existing codebase?

To assess technical feasibility, this skill parses natural language feature requests and performs codebase discovery via grep and glob to evaluate scope, complexity, and risks against existing project modules.

How do I convert natural language ideas into structured JSON issue specifications?

You can convert natural language ideas into structured JSON issue specifications by invoking this skill, which analyzes intent and generates ready-to-use issue specs including titles, descriptions, and labels.

What is the best way to scope vague feature requests into actionable development tasks?

Scoping vague feature requests into actionable tasks is done by analyzing the request, identifying affected project modules through codebase discovery, and generating a structured implementation plan.

Do I need an orchestrator-managed workflow to analyze codebase feasibility securely?

Yes, an orchestrator-managed workflow is required to delegate analysis to a permission-bypassing agent, ensuring secure code evaluation during the feasibility and scoping process.

Can I use this scoping skill with a specific platform or issue-tracking system?

This scoping skill operates by generating structured JSON issue specifications, which can be integrated with various issue-tracking systems that accept JSON input for titles and descriptions.