cognitive

Plugin cognitive from marketplace digital-stoic-marketplace in digital-stoic-org/agent-skills. Commands read from the repo's manifest — 3 days ago.

Skills (8)

• benchmark-praxis

  Benchmark Praxis methodology against external frameworks, tools, or approaches. Use when: benchmark, compare praxis, how does praxis compare, gap analysis, benchmark vs, assess against, track changelog, watch features, inventory features, full feature sweep. Modes: full (default), quick, gap, track,

• brainstorm

  Divergent-convergent brainstorming with research, ideation, and trade-off analysis. Use when exploring options, generating ideas, comparing approaches. Triggers include "brainstorm", "explore options", "ideate", "compare approaches".

• challenge

  Challenge, push back, play devil's advocate on AI output or intentions. Use when: challenge this, are you sure, push back, prove it, what if you're wrong, devil's advocate, stress test, poke holes, second opinion, sanity check, too confident, really?, question this decision, avant de commencer, je v

• experiment

  Chaotic domain: act to impose minimal constraints when cause-effect is invisible. Use when: production down with gibberish logs, completely novel problem, crisis, deliberate disruption, nothing makes sense. NOT for problems with any visible pattern — use /probe instead.

• frame-problem

  Sense-making before action. Classify problem using Cynefin triangulation (3 tests + decomposition) to route to the right skill chain. Use when: frame, what approach, how should I start, which skill, where to begin, unsure what to do. NOT for known tasks — just do them.

• investigate

  Deep proactive analysis for complex technical problems requiring upfront thinking and design. Use when: investigate, deep dive, technical spike, design strategy, complex multi-constraint problem, figure out how to, how should I approach. NOT for errors (use troubleshoot) or option brainstorming (use

• probe

  Safe-to-fail experiment for Complex domain problems where cause-effect is only visible in retrospect. Two-phase: foreground qualify → background probe → sense result. Use when: probe, safe-to-fail, test hypothesis, experiment with hypothesis, Complex domain with hypothesis. NOT for brainstorming (us

• troubleshoot

  Use when user reports an error, bug, or something not working. Search-first troubleshooting with diagnostic phase. Triggers: debug, error, broken, not working, failing, crash, exception.