- Home
- Skills
- Martinffx
- Claude Code Atelier
- Atelier Oracle Challenge
atelier-oracle-challenge_skill
- JavaScript
4
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill martinffx/claude-code-atelier --skill atelier-oracle-challenge- SKILL.md3.9 KB
Overview
This skill provides a structured critical-thinking challenger for technical decisions and implementation plans. It helps teams and developers surface hidden assumptions, test evidence, and evaluate risks before committing to architecture, patterns, or design choices. Use it to prevent automatic agreement and to get concise, actionable pushback tailored to your context.
How this skill works
You submit a concise challenge prompt describing the approach or decision you want questioned. The skill parses the request to extract the core concern, the target approach, and relevant context, then runs a sequential critical-thinking analysis through a set of focused prompts. The output highlights assumption validity, contradictory evidence, alternatives, risk trade-offs, and a recommended next step or mitigations.
When to use it
- Before major decisions: architecture, stacks, or pattern selection
- When implementation or design feels overly complex or misaligned
- To validate assumptions behind performance, scaling, or security choices
- When you need independent, rigorous pushback to avoid groupthink
- Prior to committing to costly migrations or long-lived infrastructures
Best practices
- Provide concise context: goals, constraints, and current approach
- Include specific metrics or evidence if available (performance numbers, error rates)
- Frame the prompt as a single decision or assumption to keep analysis focused
- Ask for alternatives and risk mitigations, not just criticism
- Use iteratively: run the challenge early, then re-run after changes
Example use cases
- Questioning whether microservices are justified for a small app and asking for simpler alternatives
- Challenging a proposed caching strategy that may degrade latency under load
- Testing whether event sourcing is appropriate for a given domain and team skillset
- Validating whether a chosen persistence model will meet future scalability needs
- Evaluating trade-offs of adopting a new language or framework across the codebase
FAQ
A short prompt describing the decision, the expected benefit, constraints (time, team, budget), and any supporting data produces the most targeted analysis.
Is this a replacement for design review meetings?
No. Use this skill to strengthen design reviews by surfacing blind spots and concrete alternatives; follow up with team discussion for alignment and implementation planning.