Skip to content
cccskills
FreePublished on GitHub

consulting-analysis

Structure source-grounded consulting-style analysis for strategy, market, product, operations, or decision memos. Use for MECE problem framing, hypotheses, options, tradeoffs, executive recommendations, or "consulting analysis" requests; do not use for legal/financial advice, implementation, data computation, chart rendering, or unsourced business claims.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Consulting Analysis

Purpose

Convert an ambiguous business or product question into a clear, evidence-backed recommendation with assumptions, options, risks, and next decisions.

When to Use

Use for:

  • strategy memos, product/business case analysis, market-entry framing, operational diagnosis, or option comparison
  • MECE issue trees, hypotheses, criteria, tradeoff tables, and executive summaries
  • turning research notes into a decision-ready recommendation

Do not use for:

  • regulated legal, investment, tax, medical, or HR advice
  • numeric analysis of a dataset; use data-analysis
  • chart design; use chart-visualization
  • implementing the recommendation

Workflow

  1. Clarify the decision owner, decision deadline, success metric, constraints, and non-goals.
  2. Frame the problem as a decision question, then split it into MECE drivers or hypotheses.
  3. Inventory evidence by source type and reliability. Mark assumptions separately from facts.
  4. Compare options against explicit criteria: impact, cost, speed, risk, reversibility, evidence strength, and strategic fit.
  5. Synthesize a recommendation plus alternatives, not just a list of pros/cons.
  6. State what would change the recommendation and what evidence should be gathered next.

Authenticity Rules

  • Do not invent market sizes, competitor facts, customer quotes, financial projections, or benchmark numbers.
  • If the user supplies estimates, label them user-provided unless independently verified.
  • Keep confidence tied to evidence quality; weak evidence can still support a hypothesis, not a final claim.

Output Contract

STATUS: ANALYZED | PARTIAL | BLOCKED

DECISION QUESTION:
- <question, owner, timing, constraints>

EVIDENCE LIMITS:
- <assumptions, missing sources, or conditions that would change the recommendation>

ISSUE TREE / HYPOTHESES:
- <driver or hypothesis> - Evidence/assumption:

OPTIONS:
- <option> | impact | cost | risk | reversibility | evidence strength

RECOMMENDATION:
- <recommended option and why>

RISKS / WATCHPOINTS:
- <risk and mitigation>

NEXT EVIDENCE:
- <source or experiment that would change confidence>

Provenance

Clean-room AILI/OpenCode adaptation inspired by the public DeerFlow consulting-analysis skill pattern. No upstream skill text, runtime paths, tools, generated assets, or provider assumptions are copied. Source family: bytedance/deer-flow, MIT License.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

See all skills by Rosetears520

Report a problem with this skill