Skip to content
Skills Library
Management & product · Analysis

solutioning

/solutioning

Explores solution options when the problem is defined but the approach is unclear. Use when evaluating approaches, comparing alternatives, or choosing between options.

Repository
rageatc-oss ↗
Licence
MIT
Last repository change
19.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Explores solution options when the problem is defined but the approach is unclear. Use when evaluating approaches, comparing alternatives, or choosing between options.

Original author description

Explores solution options when the problem is defined but the approach is unclear. Use when evaluating approaches, comparing alternatives, or choosing between options.

How it works

  1. Workflow
Original SKILL.md headings · 83 lines, 547 words
SKILL.md preview
---
name: solutioning
description: Explores solution options when the problem is defined but the approach is unclear. Use when evaluating approaches, comparing alternatives, or choosing between options.
---

# Solutioning

Facilitate choosing an approach when the problem is defined but the direction isn't. Explore options with the user, filter through simplicity, and record the decision for handoff to `creating-briefs`.

Skip when only one viable option exists, the user has already committed to an approach, the choice is purely preferential, or the problem itself is still unclear (`understanding-the-ask` first).

## Workflow

### Step 1 — Classify the decision

Ask: "How expensive would this be to reverse? If we try it and it doesn't work, can we go back?"

- **Reversible (two-way door)** — file structure, naming, process experiments. Decide quickly at 70% confidence and course-correct as you learn. Watch for analysis paralysis.
- **Irreversible (one-way door)** — core architecture, database selection, major dependency. Invest in understanding trade-offs before committing. Watch for premature commitment.

The classification sets the evaluation depth for everything below.

### Step 2 — Establish the simplicity baseline

"What's the simplest thing that could possibly work? Do we need this now, or are we anticipating future needs?" The simplest viable option becomes the baseline every other option must beat.

- **YAGNI** — "we might need X later" → "do we need X now? If not, add it when we do."
- **KISS** — "option A is more capable but complex" → "does simpler option B solve the current problem? Then complexity needs justification."
- **Occam's Razor** — prefer the option making the fewest assumptions about the future.

### Step 3 — Generate options

The first option presented becomes the implicit default — challenge it deliberately: "We've discussed option A; what would option B look like?" "If we couldn't do that, what would we try instead?"

Stop at 2–4 meaningfully distinct options, or when the user confirms the main approaches are covered.

### Step 4 — Compare

- **Reversible:** relative comparison to the baseline — better (+), worse (−), or same (S) per criterion. "For implementation speed, is option B better, worse, or the same as the baseline? For maintainability?"
- **Irreversible:** explicit pros and cons per option, grounded in current needs, concrete impacts, and real constraints.

Traps:

- **Confirmation bias** — "what could prove this option wrong?"
- **Analysis paralysis** — "do we have enough for a 70% confident decision?"
- **Undefined words** — "scalable", "flexible", "robust": "10x users or 1000x? What specifically?"

### Step 5 — Decide and record

Commit when: (reversible) 70% confident and genuinely reversible; (irreversible) trade-offs understood, assumptions challenged, and the choice serves current needs rather than anticipated futures.

Record the decision — lightweight ADR, 1–2 plain-language paragraphs per section, saved to the work directory:

```markdown
# Decision: [Short Title]

**Date:** YYYY-MM-DD
**Status:** Committed

## Context

[2–3 sentences: what problem were we solving? Why did this decision matter?]

## Options Considered

1. **[Option]** — [one line]
2. **[Option]** — [one line]

## Decision

We chose [option] because [primary reason].

- We gain: [main benefits]
- We accept: [costs or limitations]
- We assume: [assumptions made]

## Consequences

- [What this enables]
- [What this constrains or rules out]
- [What we'll monitor or revisit]
```

### Step 6 — Hand off

Pass the decision record to `creating-briefs`: the chosen approach, accepted trade-offs and assumptions, and what needs to be created. Done well, the brief can be written without re-exploring alternatives.

Versions

The database has no other skills named solutioning.

Database snapshot: 13.11.2026 · package version e89819c255c7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100options
    Use when several plans, architectures, or solution approaches need comparing and ranking, or the user asks for options.
  • 100brainstorm
    You MUST use this skill before /pm when work is ambiguous, scope is unclear, or multiple approaches exist. Explores problem space, proposes 2-3 approaches with trade-offs, and produces an approved spec document that feeds into both issue creation (/pm) and implementation…
  • 100compare
    Compare multiple alternatives using explicit criteria, weighted scoring, and tradeoff analysis. Use when choosing between options, evaluating alternatives, or making decisions.
  • 100evaluate-options
    Research and evaluate implementation options before presenting a recommendation. Use when multiple approaches exist for a problem and a decision is needed. Launches one background research agent per option in parallel, collects evidence-backed findings, then presents a…
  • 100solution-design
    Explores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or…
  • 100design-exploration
    Use when exploring design approaches, evaluating alternatives, or making architectural decisions. Triggers: 'explore options', 'explore design options', 'design alternatives', 'evaluate approaches', 'design tradeoffs', 'what are the tradeoffs', 'how should I approach', 'sketch…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.