Analyze an idea or signal

A case is a durable unit for any consequential idea or signal that needs explicit alternatives, tradeoffs, and a recommendation. That can be a feature, a product change, a positioning or go-to-market move, a strategy shift, or a platform and ecosystem decision.

Create a case

/deliberate case <idea>

This is the command for every case. The agent host infers one durable primary decision lens and asks only when the choice is genuinely ambiguous.

Lens	Use it for
product & experience	A customer capability or experience.
market & commercial	Audience, positioning, pricing, packaging, distribution, launch, or sales.
strategy & portfolio	Where to play, how to win, priorities, portfolio, resources, or capabilities.
platform & ecosystem	Build, buy, adopt, integrate, migrate, partner, choose a standard, or manage a dependency.

Move from decision to commitment

Every case moves through frame → shape → launch, using methods and templates suited to its lens:

1. Frame establishes the decision, evidence, current state, constraints, and stakes.
2. Shape compares alternatives and tradeoffs, then recommends a bounded direction.
3. Launch turns the recommendation into clear next commitments.

Each one-pager.md fits its audience: a product reverse PR-FAQ, market decision brief, strategy memo, or platform decision memo.

Score a case

/deliberate case <id> score

Scoring evaluates the completed recommendation against criteria for its lens and records evaluator provenance. It is not a substitute for judgment, and scores from different lenses are not directly rankable.

Prototype a case

/deliberate case <id> prototype

Prototyping is available only for product and market cases. A product prototype tests the primary journey in the product’s native medium; a market prototype tests a customer touchpoint. No prototype is forced for strategy or platform cases.

Use the id printed when the case is created, or a unique prefix. Deliberate does not keep one active case, so multiple cases can move through analysis independently.

See prototypes for how prototype artifacts fit the files-first model.

Keep direct action direct

Briefs and readouts classify follow-through as a product case, market case, strategy case, platform case, or direct action. Use a case when a consequential choice still needs alternatives and tradeoffs. Routine operations, instrumentation, already-decided work, and bounded research are direct action—not cases.