From gilfoyle
Harshly critique strategic documents (validation reports, competitive analyses, business plans) to identify blind spots, challenge assumptions, expose weaknesses, and generate Conductor-aligned action plans. Use when you need brutal honesty, "red team" analysis, or want to stress-test your thinking before execution. Applies multiple analytical frameworks (pre-mortem, assumption hunting, competitive gaps, market dynamics) and synthesizes findings into executive summaries with specific, actionable recommendations mapped to Conductor context artifacts.
npx claudepluginhub ahmedelhadarey/gilfoyle --plugin gilfoyleThis skill uses the workspace's default tool permissions.
This skill provides **harsh, unfiltered critique** of strategic documents to expose blind spots, challenge assumptions, and strengthen your plans before execution. Think of this as your personal "devil's advocate" that will **brutally honest** about weaknesses, risks, and gaps in your thinking.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill provides harsh, unfiltered critique of strategic documents to expose blind spots, challenge assumptions, and strengthen your plans before execution. Think of this as your personal "devil's advocate" that will brutally honest about weaknesses, risks, and gaps in your thinking.
Be merciless, not merciful. The goal is to find every possible flaw, weakness, and blind spot before you invest time and money. A harsh critique now saves catastrophic failure later.
Key Principles:
The user will provide one or more strategic documents to critique. Common types:
Read all provided documents completely to understand the full context.
Read references/critique_framework.md - this contains the multi-pass analytical framework with specific questions and techniques for identifying blind spots.
Systematically apply all passes from the framework:
Pass 1: Gut Check
Pass 2: Assumption Hunting
Pass 3: Pre-Mortem (Imagine Failure)
Pass 4: Competitive & Market Blind Spots
Pass 5: Synthesis
Create a comprehensive critique report with the following structure:
Organize findings by category:
Strategic Concerns
Assumption Gaps
Competitive/Market Oversights
Execution Risks
For each finding:
Generate a prioritized, specific action plan that maps recommendations to Conductor context artifacts.
For each action item:
product.md, tech-stack.md, workflow.md, etc.)Conductor Artifact Mapping Guidelines:
product.md - Update for: vision changes, feature prioritization, target user refinements, success metricsproduct-guidelines.md - Update for: messaging, positioning, brand voice, terminologytech-stack.md - Update for: technology choices, dependencies, infrastructure, scalability concernsworkflow.md - Update for: development practices, quality gates, validation processes, risk mitigation stepstracks.md - Create new tracks for: validation experiments, research tasks, prototypes, risk mitigation projectsSave the critique report as a markdown file in the project root with a descriptive name:
[ProjectName]_Critique_Report_[Date].mdProvide a brief summary of:
A good critique is:
A bad critique is:
When analyzing, actively ask:
Don't just identify risks - think through consequences:
For each competitive advantage claimed:
Challenge solution-fit from user perspective:
This skill supports the Conductor methodology at two levels:
The loop-plan-evaluator agent uses this skill's critique framework for deep plan analysis when a plan needs strategic scrutiny beyond standard scope/overlap checks.
Loop Agent Integration:
loop-plan-evaluator → may invoke plan-critiquer for strategic-level plan reviewloop-execution-evaluator → may invoke plan-critiquer for post-mortem analysisThe critique acts as a quality gate - don't proceed to spec/plan until critical blind spots are addressed.
The skill uses assets/critique_template.md as the base structure. Customize sections as needed for the specific documents being critiqued, but maintain the core structure: