Questions about Ritual and Exploration

Ritual solves context drift. AI can now generate answers, documents, specs, plans, and code very quickly. The harder problem is making sure those outputs are grounded in the right problems, questions, constraints, and tradeoffs. Without strong context, AI tools often produce work that looks plausible but misses important issues, creates rework, or requires many rounds of correction. Ritual helps teams do structured discovery before they generate output. The result is fewer blind spots, fewer unnecessary loops, and outputs that are easier to trust, review, and act on.

Ritual is for individuals or teams working on complex problems that require exploration.

One of our key markets is developers and engineering teams using AI coding tools, because context drift shows up very clearly when agents start building from weak specs or vague prompts. But Ritual is not only for developers. Product teams use Ritual to create stronger requirements. Strategy and transformation teams use it to explore cross functional initiatives. Any team using AI to create important deliverables can benefit from Ritual when they need better discovery, better reasoning, and stronger context before moving to execution.

Instead of asking AI to jump straight from a prompt to an output, Ritual helps create the structured context AI needs to produce better work.

It does this through a discovery-to-recommendations workflow. Ritual builds a structured graph of the problem space, identifies sub-problems to explore, generates discovery questions, reasons through the answers, and produces explainable recommendations based on that exploration.

Once the recommendations look right, you can use that stronger context to generate the deliverable you need, whether that is code, a spec, a PRD, a business case, or another important document.

You can leverage Ritual inside an AI tool (Claude, ChatGPT, Codex, v0, etc) by installing our plug-in.

Alternatively, you can also use Ritual through our desktop app. The app provides a dedicated workspace for each problem you are exploring and guides you through the key steps, from problem scoping to curating discovery questions to working through recommendations. When the workflow is complete, you can generate a stronger deliverable from the context you have built.

Ritual helps developers move from prompt to PR with less drift and rework. It runs inside the developer environment through MCP, so builders can invoke Ritual before an AI coding agent starts implementation. Ritual turns the feature, fix, or technical problem into a context-rich build brief that the agent can use in its planning step.

That brief captures the scope, implementation considerations, edge cases, tradeoffs, dependencies, and reasoning behind the recommended approach. Instead of asking an agent to infer too much from a vague prompt or incomplete spec, Ritual gives the agent stronger execution context up front. The result is better first-pass code, fewer unnecessary turns, and reviews grounded in the reasoning behind the work.

Ritual was built for complex work across the business. Product, strategy, operations, marketing, transformation, and leadership teams can use Ritual to reason through ambiguous problems and produce stronger deliverables, including plans, requirements, business cases, marketing briefs, and strategy documents. You can use Ritual's desktop app. Alternatively, you can install Ritual inside other AI tools so the discovery workflow is available where work already happens. In either case, Ritual helps create stronger context before AI generates the final output.

Most AI tools help you generate an output. Ritual helps improve the thinking and context before the output is generated.

Ritual creates a structured representation of the problem space, and its workflow helps resolve ambiguity step by step by turning unknowns into discovery questions, answers, reasoning paths, and explainable recommendations before generating output.

That makes Ritual complementary to existing AI tools. It does not replace your coding agent, LLM, workspace, or development tool. It strengthens the context those systems rely on.

Ritual is designed to fit into the tools where work already happens. For developers, Ritual can run through MCP inside the developer environment, helping create context-rich build briefs before agents code and preserving the reasoning path behind implementation choices for review in tools like GitHub.

For product managers, Ritual outputs can feed tickets, stories, requirements, or planning artifacts in tools like Jira. Designers can take stronger specifications into prototyping tools. Strategy, operations, and transformation teams can turn Ritual recommendations into tactics, workstreams, and project plans.

You can use Ritual individually or collaboratively. A developer might use Ritual to create a stronger build brief before handing work to an agent. A product manager might use it to clarify requirements before creating tickets. A strategy or operations leader might use it to develop better recommendations before sharing a plan.

If you are working with a team, Ritual supports rich collaboration by letting you invite others into the discovery workflow so they can contribute directly. You can also gather input through meetings, interviews, workshops, or other formats, then bring that input into Ritual by uploading transcripts or source material. Team adoption can grow organically. Ritual can start with one person improving the quality of the work, then expand as teams see the value of shared discovery, shared context, and better-reasoned outputs.

There are two ways to get started with Ritual.

First, developers can set up Ritual in two ways: through the Ritual CLI or by connecting Ritual's MCP server directly to their coding agent. The CLI path installs Ritual globally, runs ritual init inside a project, and auto-configures detected agents with MCP and the /ritual skill. The direct MCP path lets teams wire Ritual straight into tools like Claude, v0.dev, or other supported agents without using the CLI.

Second, individuals and teams can use the Ritual desktop app. The app provides a dedicated workspace for each problem, guiding users from problem scoping to discovery questions, reasoning, recommendations, and final deliverables.

Yes, but Ritual is not a traditional knowledge base. Most knowledge management systems store information so people can find it later. Ritual makes knowledge reusable by capturing the reasoning behind work: the problem being explored, the sub-problems, discovery questions, answers, assumptions, tradeoffs, evidence, recommendations, and decisions. That creates an instructional knowledge base teams can use again. If someone revisits a feature, strategy, requirement, or initiative months later, they can see not just what was decided, but why it was decided. Ritual helps preserve institutional knowledge as structured context that people and AI tools can use before doing the next round of work.