Skip to the usage guide
Parallel Conceptsby owl-listener

Parallel Concepts Skill.

Explore different ways users could complete the same task.

  • Concept Exploration
  • Alternatives
Source Review · parallel-conceptsSKILL.md
Task Explore different ways users could complete the same task. Produces A set of behaviorally distinct concepts addressing one agreed problem. Before You Start Bring one agreed user problem, the current proposal and the uncertainty worth exploring. Set a fidelity and effort budget so alternatives can be compared on behavior rather than presentation polish.
Editorial summary · source reviewed 2026-11-02 · not a generated example

01 What It Does

Explore different ways users could complete the same task

Develop comparable design concepts that vary interaction sequence, responsibility or commitment while holding visual treatment steady.

Source-based workflowNot an execution benchmark

The Working Approach

Parallel Concepts explores multiple solutions to a problem before a team commits to refining its first idea. The source defines a meaningful alternative through user behavior: different steps, a different unit of interaction or a different division of work between user and system. Changing a color palette around the same flow does not create another concept.

The skill keeps options at comparable fidelity and gives each a clear question to test. It chooses the breadth of exploration according to cost and stakes, then leaves selection to a separate workflow. This is useful early, while testing an alternative can still cost a sketch rather than a finished build.

Expected Deliverables

  • A set of behaviorally distinct concepts addressing one agreed problem.
  • An explicit question or assumption tested by each concept.
  • Comparable-fidelity artifacts ready for a separate selection step.
See the Example Brief

From Brief to Review

  1. 01
    Name the exploration question

    Start with a problem and the proposed solution already on the table. Identify the uncertainty that another approach could resolve.

  2. 02
    Choose meaningful differences

    Vary sequence, interaction unit, division of labor, entry point or commitment point. Keep the visual language constant so decoration does not become the test variable.

  3. 03
    Build a defensible set

    Give each concept comparable effort and fidelity. Drop duplicate or implausible directions and keep the set small enough for the available exploration budget.

  4. 04
    Prepare for comparison

    Explain what each concept tests and preserve the alternatives. Hand them to a separate decision process rather than ranking them prematurely.

02 When to Use It

When to Use It

Bring one agreed user problem, the current proposal and the uncertainty worth exploring. Set a fidelity and effort budget so alternatives can be compared on behavior rather than presentation polish.

A Good Fit

  • One idea has become the defaultA team wants to investigate alternatives before committing to refinement.
  • Behavior is uncertainThe important choice concerns workflow or responsibility rather than visual styling.

Limits to Check

  • Exploration scopeThe source does not rank or eliminate concepts; selection is a separate skill.
  • Equal presentationMismatched fidelity can bias comparison toward the more polished option.
  • Real alternativesA deliberately weak option or a cosmetic duplicate does not contribute useful evidence.

Bring These Inputs

  • Agreed problemState the user task and the current proposed approach.
  • Decision uncertaintyName what the competing concepts should help the team learn.
  • Exploration budgetProvide constraints on fidelity, effort and feasible implementation.

03 Decisions That Matter

Decisions That Matter

  1. Behavioral breadth

    Alternatives expose assumptions about how the task must work.

  2. Fair comparison

    Similar fidelity reduces the chance that presentation quality decides the outcome.

  3. Reusable exploration

    Each concept carries a testable reason for existing.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Source and Setup

State the user task and the current proposed approach.

Upstream Source File
https://github.com/owl-listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/prototyping-testing/skills/parallel-concepts/SKILL.md

The reference below opens the upstream instructions. Review the repository setup before using them; it is not an installation command.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use parallel-concepts to explore our bulk file-import experience before we refine the current wizard. The user needs to review and correct invalid records before committing the import. Develop three feasible concepts that differ in behavior, such as when validation happens or whether corrections are handled individually or in batches. Keep the visual language and fidelity consistent. State the assumption each concept tests and the interaction sequence the user follows. Preserve the current idea as one option. Do not rank the concepts or create a deliberately weak alternative.

Inspect the Result

Check the actual output against these observable criteria.

  • Each concept changes what the user does, not only its appearance.
  • Options address the same problem at comparable fidelity.
  • Every concept has a stated learning question and could plausibly be built.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
owl-listener
Skill File
SKILL.md
License
MIT
Reviewed Snapshot
2026-11-02 · 9a6930cf84a8
Editorial Source Summary
Explore different ways users could complete the same task.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

How many concepts should it produce?

The source makes the count depend on cost and stakes, rather than a fixed target.

Does it choose the winner?

No. It prepares divergent alternatives for a separate concept-selection step.

Can two visual styles count as two concepts?

The source treats identical task steps with different visual treatments as one behavioral concept.

OpenDesign

Keep Your Brief and Design Work Together.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Upstream Source File
https://github.com/owl-listener/designer-skills/blob/9a6930cf84a822eb458624bd11c61aac5bbdf224/prototyping-testing/skills/parallel-concepts/SKILL.md