One-click install
npx skills add https://github.com/qvidal01/claude-code-skills --skill ideate-qvidal01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideate
Source: https://github.com/qvidal01/claude-code-skills/tree/main/ideate
Command: npx skills add https://github.com/qvidal01/claude-code-skills --skill ideate-qvidal01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill generates feature and improvement ideas by grounding them in existing audit artifacts, ensuring that all suggestions are backed by real evidence and findings from the audit.

Core Features & Use Cases

  • Audit-Based Ideation: All ideas must reference RISK-### or UNK-### IDs from an audit artifact, ensuring evidence grounding.
  • Flexible Invocation: Customizable via stage, categories, and forced stale for different use cases.
  • Ideas Categorization: Organizes ideas by categories like Code Improvements, UI/UX, Documentation, and more, allowing focused ideation.

Quick Start

Use /ideate to generate evidence-based feature ideas for the latest audit.

Frequently Asked Questions about ideate

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

FAQPage Schema
How do I generate feature ideas from software audit findings?

To generate feature ideas from software audit findings, use evidence-based ideation to process existing RISK and UNK IDs, ensuring all improvement suggestions are grounded in real audit artifacts.

What is evidence-based feature ideation for software projects?

Evidence-based feature ideation is a process that generates concrete software improvements by categorizing ideas into Code, UI/UX, and Documentation based strictly on referenced findings from post-audit review artifacts.

Can I categorize software improvement ideas by specific audit stages?

Yes, you can categorize software improvement ideas by specific audit stages, applying customizable category filters like Code Improvements and Documentation to organize evidence-based output during post-audit reviews.

Do I need existing RISK or UNK IDs to generate improvement ideas?

Yes, you need existing RISK or UNK IDs to generate improvement ideas, because the system requires referencing specific audit artifacts to ground all feature suggestions in verified project findings.

What's the best way to drive project enhancements after a code audit?

The best way to drive project enhancements after a code audit is to run evidence-based ideation, which automatically translates raw audit artifacts into categorized, actionable software improvements.