ce:ideate

Generate grounded improvement ideas from repository context into docs/ideation/ artifacts.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-ideate-mukles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:ideate
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/ce-ideate
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-ideate-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and critically evaluate grounded improvement ideas for the current project, ensuring ideas are rooted in the actual codebase and organizational context to prevent theory-only brainstorming.

Core Features & Use Cases

  • Grounded ideation workflow: multi-phase process that first surfaces ideas, then critiques and ranks them against the repository context.
  • Codebase grounding: ties suggestions to observable aspects of the project and existing docs or issues.
  • Collaborative and scalable: uses multiple frames and agents to diversify ideas while preserving focus on the repo.
  • Artifact production: outputs a structured ideation artifact under docs/ideation/ for traceability and handoff.
  • Use Case: ask for improvements, new directions, or radical reframes, then review survivors before a brainstorm.

Quick Start

Propose a focused topic and I will generate a multi-phase, grounded ideation set and present survivors for review.

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?

Grounded ideation anchors improvement suggestions in the actual repository context, tying ideas to existing docs, issues, and observable codebase aspects to prevent theory-only brainstorming.

What is the best way to brainstorm new directions for a software project?

A collaborative ideation workflow uses multiple frames to diversify ideas while preserving focus on the repository, ranking survivors to steer proactive directions before deep brainstorming.

How do I document ideation artifacts for traceability and handoff?

Output a structured ideation artifact under docs/ideation/ to record grounded survivors, ensuring traceability and handoff for the project.

Can I steer the ideation process toward specific areas of a repository?

Yes, you can provide optional focus hints to steer the framing of the ideation workflow, directing the multi-phase process to generate and critique ideas within specific boundaries.

Does this ideation workflow work without external dependencies?

Yes, the grounded ideation workflow operates without external dependencies, relying entirely on the current project's codebase and organizational context to generate and evaluate improvement ideas.