forge:ideate

Analyze FORGE project codebase across five lenses to surface weaknesses and improvements.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-ideate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge:ideate
Source: https://github.com/Chulf58/FORGE/tree/main/skills/ideate
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-ideate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ideator helps teams quickly surface weaknesses, missing capabilities, risky patterns, and improvement opportunities in a codebase by performing adversarial analysis in read-only mode.

Core Features & Use Cases

The ideator analyzes the project from five lenses—fragility, missing capabilities, technical debt, security/safety, and user experience gaps—and emits [todo] signals for actionable improvements. It surfaces up to ten findings, each referencing a specific file or module. It is intended for use when a user asks for improvement ideas, a critical review of the project, or to identify what should be fixed.

Quick Start

Invoke the ideator agent to perform adversarial analysis of the project and generate actionable improvement findings.

Frequently Asked Questions about forge:ideate

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

FAQPage Schema
How do I find weaknesses and improvement opportunities in a codebase?

Adversarial codebase analysis examines a project through five lenses—fragility, missing capabilities, technical debt, security/safety, and UX gaps—to surface up to ten actionable findings with specific file references.

What is adversarial codebase analysis and how does it work?

Adversarial codebase analysis is a read-only exploration method that identifies risky patterns and missing capabilities by critically reviewing a project across five distinct lenses, emitting structured findings with file references for non-destructive improvement.

How do I get a critical review of my project's technical debt and security?

You get a critical review by running an adversarial analysis agent that targets technical debt and security/safety lenses, surfacing up to ten structured findings with specific module references for actionable improvements.

Can I analyze codebase fragility without modifying the source code?

Yes, you can analyze codebase fragility without modifying source code because the adversarial ideation operates in read-only mode, performing non-destructive exploration to safely surface weaknesses and improvement opportunities.

What is the best way to identify user experience gaps in a codebase?

The best way to identify user experience gaps is through an adversarial analysis that specifically evaluates the UX lens of the project, generating actionable findings with references to the relevant files and modules.

How many improvement findings does an adversarial codebase review generate?

An adversarial codebase review generates up to ten findings, each structured with specific file or module references to ensure the identified weaknesses and improvement opportunities are directly actionable.