Find simpler product behavior by questioning assumed requirements and working backward from a shared vision. Use when exploring simpler workflows, settings, modes, fidelity, or scope and the product direction needs judgment.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use dialectic as the method: clarify the intent, develop the greenfield vision, then work backward from that vision. Dialectic owns the conversation and how agreed intent and vision develop through reactions. This skill contributes the product lens: question assumed requirements and find simpler behavior that makes implementation unnecessary.
Establish the job in the person's terms, including what they must be able to rely on. Treat existing workflows and guarantees as evidence of earlier choices. Ask which requirements serve that job and which the current design introduced. Keep a change to the job itself explicit.
Develop a greenfield vision of the experience that would fulfill the intent. A recurring choice might be resolved once, a mode or degree of fidelity might be unnecessary, or actions might belong together or deserve separate decisions. A native primitive may already do the work. Compare concrete experiences when their differences help the person judge the direction.
Show what the person does, what becomes easier, what they lose, and what obligations remain. Account for mechanisms added as well as removed, including work shifted to the person or a later step. Include interruption and failure when they change the choice. Distinguish possible deletions from claims traced against the code. Keeping a capability is a valid outcome when it earns its complexity. Removing features, steps, or state is a consequence, not the goal.
Derive the owners and mechanisms from the recognized behavior, using what already does the job before adding an owner. Before calling state redundant, identify the information it carries and establish that the replacement has it whenever needed. Preserve work, evidence, and decisions with no other owner. Check that complexity disappears rather than moving into another store, service, or implicit user obligation.
Use collapse-pass to carry an authorized change through its callers, remove what it made unnecessary, and verify the result. Use disposable data for app experiments. Use asymmetric-wins to judge a particular small promise whose refusal could delete disproportionate complexity.
Read the examples for product decisions developed through this method. They illustrate questions to examine, not transformations to apply by keyword or a required number of alternatives.
EpicenterHQ/epicenter
04f87cb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.