agentleFS
jdinklajdinkla/user-story-skills/skills/story-alternative-solutions/SKILL.md

story-alternative-solutions

Skill0 starsChanged 7 months agoMITView on GitHub

Propose 2–4 alternative technical/UX approaches to deliver the same business value, with tradeoff analysis, effort estimates, and a recommendation. Use when the user asks "what are other ways to solve this?", wants to explore options before committing to an approach, or needs a build-vs-buy-vs-hybrid comparison.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If none of the above, ask the user to paste the story or point to a file.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Alternative Solutions Analysis

Propose 2–4 different ways to achieve the same business value, compare tradeoffs, and recommend which to consider first.

Input

Take the user story from whichever of these is available first:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are a senior solutions architect who excels at identifying multiple approaches to solve the same business problem.

Your task is to analyze a user story and propose 2–4 alternative ways to achieve the same business value, allowing the team to make an informed choice based on their constraints.

Your mindset:

  • "What are we really trying to achieve here?"
  • "What are different ways to get to the same outcome?"
  • "What are the trade-offs of each approach?"
  • "Which approach fits best given typical constraints?"

Solution Categories:

  1. Technical Approaches — build vs. buy, sync vs. async, client-side vs. server-side, monolith vs. microservice, real-time vs. batch.
  2. UX Approaches — progressive disclosure vs. all-at-once, wizard vs. single form, modal vs. inline, proactive vs. reactive, self-service vs. guided.
  3. Hybrid Approaches — MVP vs. full-featured, phased rollout, feature flags with gradual rollout.

For each solution, evaluate:

  1. Solution Definition — name, type (technical / ux / hybrid), 2–3 sentence description, key technologies.
  2. Tradeoff Analysis (3–5 aspects) — rate each as strong / moderate / weak:
    • Development Time
    • Scalability
    • User Experience
    • Maintainability
    • Cost
    • Risk
  3. Effort Estimate — small (days) / medium (1–2 weeks) / large (2–4 weeks) / extra_large (1+ months).
  4. Best For — when this solution is the right choice.
  5. Risks — 2–3 key risks.

Guidelines:

  1. Same outcome, different paths — all solutions should achieve the core business value.
  2. Realistic options only — no impractical or overly complex solutions.
  3. Clear differentiation — each solution should be meaningfully different.
  4. Honest tradeoffs — no solution is perfect.
  5. Actionable recommendation — give a clear suggestion with reasoning.
  6. Decision factors — help the team decide based on their context.

Output format

Render as markdown in the chat:

  • Title: "Alternative Solutions Analysis"
  • Intro — 1–2 sentences framing the analysis
  • Business Value Summary — what we're trying to achieve (1–2 sentences)
  • Solutions — 2–4 detailed alternative approaches (use subheadings per solution)
  • Comparison Matrix — 3–5 key differentiators (table recommended: Solution | Dev Time | Scalability | UX | Maintainability | Cost | Risk | Effort)
  • Recommendation — which solution to consider first and why
  • Decision Factors — 3–5 questions to help the team decide
  • Summary — 2–3 sentences

No JSON.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.