When is the best time to use this skill?

It is most effective during the planning or design phase, particularly when you have a proposal that feels complex or high-stakes.

How does the challenge skill help my development workflow?

It acts as a critical second pair of eyes, identifying hidden risks and simpler alternatives to your technical proposals before you commit to writing code.

Can it help prevent over-engineering?

Yes, one of its core instructions is to look for a simpler version of the proposal that captures 80% of the value with less complexity.

Does it check for conflicts with my current codebase?

Yes, it specifically analyzes if your proposal creates tension with existing specs, patterns, or previous architectural decisions in your project.

Is the feedback from /eidos:challenge adversarial?

No, the skill is specifically designed to be collaborative and constructive, starting from the assumption that your idea has merit while looking for ways to make it stronger.

Constructive Proposal Challenge

Name: Constructive Proposal Challenge
Author: agenticnotetaking

byagenticnotetaking

•

コラボレーションツール

Identifies blind spots, risks, and alternatives in technical proposals through structured, non-adversarial feedback.

The /eidos:challenge skill acts as a virtual peer reviewer, helping developers and architects refine their ideas before implementation. By systematically analyzing proposals for hidden risks, simpler alternatives, and potential architectural tensions, it ensures that technical decisions are well-vetted and robust. It moves beyond simple validation to provide critical thinking that surfaces what might have been missed, all while maintaining a collaborative and supportive tone that assumes the initial idea has merit.

主な機能

0136 GitHub stars

02Risk assessment to detect future pain points and potential failures

03Systematic identification of architectural blind spots and missing details

04Evaluation of simpler alternatives to capture 80% of value with less effort

05Conflict detection with existing specifications, patterns, or project decisions

06Actionable final assessments with clear next steps for refinement

ユースケース

01Vetting a new feature architecture before starting the implementation phase

02Refining a complex refactoring plan to minimize risks and technical debt

03Reviewing a technical design to find simpler, more maintainable solutions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add agenticnotetaking/eidos challenge

For use in Claude.ai and ChatGPT

Download Skill