Skip to content

fzfclee/consulting-skills / skills/min-specs

min-specs

Verified

Use when a plan, partnership, deal, product, change, or stakeholder move needs the minimum necessary conditions for success. Use when applying Min Specs, minimum specifications, must-have constraints, no-go criteria, or success conditions.

Min Specs

Use this skill to define the smallest set of must-have conditions that make an action viable.

Method Notes

  • Min Specs identify what is truly required, not a wish list.
  • The method helps prevent overbuilding, over-negotiating, and pursuing deals that cannot work.
  • A good Min Spec is binary enough to guide proceed / adjust / stop decisions.

Required Inputs

Collect or infer these inputs before execution:

  • desired outcome
  • proposed action, deal, solution, or change
  • constraints and non-negotiables
  • known failure modes
  • stakeholder or customer requirements

If an input is missing, mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use when the user needs to rank attractive options rather than define viability. Use decision-matrix, weighted-scorecard, or wsjf-prioritization instead.

Step-by-Step Execution

StepRequired inputHow to executeOutput
Define successDesired outcome, decision boundary.State what must be true for the initiative to be considered successful.Success definition.
List possible requirementsStakeholder needs, constraints, risks, operating needs.Create a broad list of candidate conditions.Requirement pool.
Remove nice-to-havesCandidate requirements, success definition.Ask whether success fails without this condition. If not, move it to nice-to-have.Trimmed requirements.
Convert to minimum specsMust-have conditions.Rewrite each condition as observable, testable, and binary where possible.Min Specs list.
Define no-go criteriaFailure modes, risk tolerance, constraints.State what would make the action non-viable or require redesign.No-go list.
Link to next actionCurrent plan, validation access, owners.Decide what to confirm first and what action is allowed before confirmation.Decision gate.

Output Template

### 1. Success Definition
- Desired outcome:
- Decision boundary:
- What would count as failure:

### 2. Min Specs
| Minimum condition | Why it is required | Evidence now | How to verify | Pass / fail / unknown |
|---|---|---|---|---|
|  |  |  |  |  |

### 3. Nice-To-Haves Removed
- Nice-to-have:
- Why it is not required now:

### 4. No-Go Criteria
| No-go condition | Trigger signal | Response |
|---|---|---|
|  |  |  |

### 5. Decision Gate
- Proceed if:
- Adjust if:
- Stop if:
- First thing to verify:

Quality Gate

  • Keep Min Specs few and strict. If everything is required, nothing is clarified.
  • Avoid vague wording such as "good support" or "strong alignment"; define observable behavior.
  • Separate minimum conditions from preferences.
  • Include stop or redesign criteria.
  • Keep the output usable in a real decision conversation.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall