cohesively

Route code change requests to Cohesive workflows enforcing global coherence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When making code changes, it's easy to produce edits that work locally but break existing system rules, invariants, architectural seams, or long-term product direction. This Skill eliminates that risk by routing every Cohesive-shaped request to the correct workflow that enforces global coherence with your codebase's existing substrate of specs, tests, and institutional knowledge.

Core Features & Use Cases

  • Intelligent Request Routing: Classifies user requests into the appropriate Cohesive workflow, including the flagship Decide → Lock → Build gates, standalone diagnostics (codebase review, diff review, substrate audit), and one-time adoption initialization.
  • Change-Type Guardrail: Automatically asks a forced-choice question to distinguish between extending existing concepts and introducing new ones, routing to the correct light or full design workflow to avoid misalignment.
  • Subskill Coordination: Manages dispatch contracts and progress tracking for chained subskills, composing with Superpowers skills for implementation discipline, worktree management, and branch finishing when needed.
  • Use Case Example: Use this Skill when you want to brainstorm a refactor of a core subsystem, review a PR for cohesion with existing architecture, or audit your codebase for missing specs and invariants that should be encoded.

Quick Start

Ask the AI to "cohesively brainstorm a refactor of the user authentication flow" to get a recommended design direction with risk mitigation and structural next steps.

Frequently Asked Questions about cohesively

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

FAQPage Schema
How do I ensure my code refactoring aligns with existing system architecture and invariants?

To ensure code refactoring aligns with existing architecture, route requests through a workflow that enforces spec alignment, named invariants, and architectural seams. This prevents locally plausible edits from breaking globally incoherent system rules during structural changes.

What is the best way to audit a legacy codebase for missing institutional knowledge and specifications?

Auditing a legacy codebase for missing institutional knowledge requires a substrate audit workflow that identifies undocumented invariants and specifications. This process extracts encoded rules to establish a durable baseline for future coherent code modifications.

How can I review a pull request for cohesion with long-term product direction and behavior matrices?

Reviewing a pull request for cohesion involves checking diffs against existing behavior matrices and architectural seams. This enforces global coherence by validating that proposed changes do not violate established system specifications or invariants.

When do I need to distinguish between extending existing concepts versus introducing new ones during software design?

You need to distinguish between extending existing concepts and introducing new ones when initiating a code change. A change-type guardrail forces this distinction, routing the request to the correct light or full design workflow to prevent architectural misalignment.

How do I coordinate chained subskills for implementation discipline and worktree management?

Coordinating chained subskills for implementation discipline relies on dispatch contracts and progress tracking. This manages subskill execution, composing with complementary tools for worktree management and branch finishing when needed.