ce:ideate

Generate grounded improvement ideas from repository scans and ideation docs.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-ideate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:ideate
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-ideate
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-ideate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces unfocused brainstorming with a disciplined, repository-aware ideation process so teams can discover the strongest improvement directions before planning begins.

Core Features & Use Cases

  • Structured grounding: Scan docs, recent ideation, and issue themes to collect tangible signals before generating ideas.
  • Diverse ideation frames: Run multiple sub-agent perspectives and synthesize the merged list to cover friction, missing capabilities, automation, and leverage layers.
  • Adversarial filtering & artifacting: Critique every candidate, rank survivors, document the outcome in docs/ideation/, and route selected ideas to the next skills in the workflow.
  • Use Case: When planning the next sprint, ask for improvement ideas and automatically receive a ranked, critiqued set plus session log instructions.

Quick Start

Ask the assistant to generate grounded improvement ideas for the current project, citing recent docs and repository context before ranking the survivors.

Frequently Asked Questions about ce:ideate

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

FAQPage Schema
How do I generate grounded improvement ideas for my codebase?

To generate grounded improvement ideas, the Skill scans repository context, recent ideation docs, and issue themes to produce ranked, critique-informed directions across workflow, quality, and missing capabilities. It synthesizes diverse perspectives and filters candidates adversarially before documenting survivors in docs/ideation/.

What is the best way to brainstorm project improvements without unfocused planning?

Disciplined ideation replaces unfocused brainstorming by running multiple sub-agent perspectives to cover friction, missing capabilities, automation, and leverage layers. Every candidate is critiqued and ranked, ensuring teams discover the strongest improvement directions before planning begins.

How do I structure ideation sessions to evaluate high-leverage directions?

Structure ideation by scanning repository docs and recent themes to collect tangible signals, then run diverse ideation frames to generate candidates. Apply adversarial filtering to critique every candidate, rank survivors, and document the ranked outcomes ready for the next workflow stage.

Can I use codebase scanning to find missing capabilities and workflow friction?

Yes, codebase scanning evaluates high-leverage directions by analyzing repository context and recent ideation docs. It identifies friction, missing capabilities, and automation opportunities, running diverse perspectives to synthesize a merged list of grounded improvement candidates.

When do I need adversarial filtering for ideation documentation?

Adversarial filtering is needed when you must critique every generated improvement candidate to ensure only the strongest survive. It ranks the validated ideas and documents the outcome in docs/ideation/, routing selected ideas to the next skills in the workflow.

Does grounded ideation work for sprint planning and project improvement?

Yes, grounded ideation is designed for sprint planning by automatically providing a ranked, critiqued set of improvement ideas. It uses repository scans and critique-informed filtering to route selected ideas to the next skills, replacing unfocused brainstorming with structured outcomes.