跳到正文
cccskills
免费在 GitHub 公开

solution-exploration

Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Solution exploration

The most expensive bugs are decisions, not defects. This runs before implementation, not instead of it.

Establish what is actually wanted

The stated request is a proposed solution wearing the clothes of a requirement. Get underneath it:

  • What outcome does the person want? What breaks today without it?
  • Who else touches this, and what do they assume about it now?
  • What is explicitly not being asked for?
  • How will we know it worked — the observable difference.

If the answers conflict, stop and resolve that first. Building the average of two requirements satisfies neither.

Generate genuinely different options

Two variations of the same idea are one option. Force real range:

  • The smallest thing that could work.
  • The version that assumes this doubles in scope next quarter.
  • The version that requires no new moving parts.
  • Buy, borrow, or do nothing.

For each: what it costs, what it forecloses, and what has to be true for it to be right.

Converge

Recommend one and say why the others lost. A comparison that ends without a recommendation has moved the work, not done it.

Name the assumption the recommendation rests on most heavily — that is where the plan will break if it breaks.

Never

  • Present options you would not accept as padding around the one you want.
  • Skip this because the task "is simple." Simple tasks take five minutes here.
  • Let a preference stand in for a reason.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20762026年10月19日 更新

查看 cbrock84 的全部技能

报告此技能的问题