using-cohesive

Route substrate-first engineering tasks to the cohesive:cohesively router.

Updated May 7, 2026
One-click install
npx skills add https://github.com/marktoda/cohesive --skill using-cohesive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-cohesive
Source: https://github.com/marktoda/cohesive/tree/main/skills/using-cohesive
Command: npx skills add https://github.com/marktoda/cohesive --skill using-cohesive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the confusion of being misrouted between Cohesive and Superpowers when working on substrate-first engineering tasks, ensuring you land in the right workflow immediately for work involving system invariants, specs, and codebase cohesion.

Core Features & Use Cases

  • Substrate trigger detection: Identifies when your request relates to substrate-first work such as designing features that touch named invariants, reviewing code or PRs for cohesion, auditing missing system memory, rewriting specs or behavior matrices, implementing approved rewrites, or extending existing system concepts.
  • Clean Superpowers deferral: Automatically defers implementation-discipline tasks (writing tests, executing existing plans, debugging specific issues, general code exploration) to Superpowers without sending unnecessary orientation messages.
  • Use case example: If you ask to "review the PR for cohesion" or "rewrite the behavior matrix for the auth flow", this skill routes you directly to the Cohesive router instead of sending you to generic exploration or implementation workflows.

Quick Start

Request a substrate cohesion review of your current codebase or a rewrite of the existing behavior matrix for the user authentication flow to activate the correct Cohesive workflow.

Frequently Asked Questions about using-cohesive

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

FAQPage Schema
How do I route substrate-first engineering tasks to the correct workflow?

Substrate-first engineering tasks are routed by detecting triggers like invariant design, cohesion reviews, or spec rewrites, then directing you to the cohesive:cohesively router for substrate-shaped work instead of generic implementation workflows.

What's the difference between Cohesive and Superpowers workflow routing?

Cohesive routing handles substrate-first work like behavior matrix rewrites and system concept extensions, while Superpowers defers implementation-discipline tasks such as writing tests, debugging, and executing existing plans without unnecessary orientation messages.

When do I need a cohesion review for my codebase?

A cohesion review is needed when you review code or PRs for system cohesion, audit missing system memory, or work on features that touch named invariants within a substrate-first engineering context.

Can I use this workflow for spec rewrites and behavior matrix updates?

Yes, spec rewrites and behavior matrix updates are core substrate-first triggers that activate the Cohesive workflow, routing you directly to the cohesive:cohesively router for these tasks.

Does this routing apply to debugging and test writing tasks?

No, debugging specific issues, writing tests, executing plans, and general code exploration are implementation-discipline tasks automatically deferred to Superpowers without sending orientation messages.

using-cohesive: what problem does it solve for substrate-first work?

It eliminates misrouting between Cohesive and Superpowers entry points for substrate-first engineering tasks, ensuring you land in the correct workflow immediately for work involving system invariants, specs, and codebase cohesion.