cog-scenario

Model decision scenarios by generating 2-3 branches with timelines.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/bketelsen/max --skill cog-scenario
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cog-scenario
Source: https://github.com/bketelsen/max/tree/main/skills/cog-scenario
Command: npx skills add https://github.com/bketelsen/max --skill cog-scenario

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill models decision scenarios by identifying forks and generating 2-3 branches with timelines, enabling explicit exploration of futures derived from a single choice.

Core Features & Use Cases

  • Branch identification: detects a decision point and outlines alternative paths with dependencies and timelines.
  • Dependency mapping: traces upstream and downstream memory sources to ensure traceability.
  • Timeline overlay: aligns branches to real calendar events for practical planning.
  • Output generation: writes a memory/scenarios file detailing the decision, branches, and contingencies.

Quick Start

Provide a decision point and have the system generate 2-3 branches with timelines using memory data.

Frequently Asked Questions about cog-scenario

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model decision scenarios with branching timelines?

You can model decision scenarios by identifying a decision fork and generating 2-3 alternative branches with timelines. The system traces upstream memory sources for dependencies and aligns branches to real calendar events for practical planning.

What is branching scenario modeling for decision-making?

Branching scenario modeling is the process of exploring alternative futures derived from a single choice. It identifies a decision point and outlines alternative paths with dependencies and timelines to enable explicit exploration of potential outcomes.

Can I use memory data and calendars to map decision dependencies?

Yes, dependency mapping traces upstream and downstream memory sources to ensure traceability. A timeline overlay aligns these branches to real calendar events, applying memory data to influence cross-domain decision outcomes.

How do I generate a scenario file for cross-domain decisions?

Provide a decision point and the system generates 2-3 branches with timelines using memory data. It outputs a scenario file to memory/cog-meta/scenarios detailing the decision, branches, and contingencies for personal, work, or health contexts.

What is the best way to track decision forks across personal and work contexts?

The best way to track decision forks is by generating alternative paths with dependencies and timelines. This approach applies to cross-domain decisions in personal, work, or health contexts where memory data and calendars influence outcomes.

Does scenario modeling work without pre-existing memory sources?

Scenario modeling traces upstream and downstream memory sources to ensure traceability and references memory sources for dependency tracking. Providing a decision point allows the system to generate branches, but existing memory data informs the timeline and outcome alignment.