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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of implementation drifting from approved spec rewrites, ensuring all code, tests, and CI changes fully align with the locked design, cover every spec promise, and avoid unapproved divergent changes.

Core Features & Use Cases

  • Dual-mode workflow: Supports standard mode for post-validate-rewrite Approved runs and extend mode for post-rewrite-specs extension runs, adapting input requirements and reviewer dispatch to each context.
  • Substrate-anchored execution: Composes with Superpowers for TDD-disciplined plan writing and execution, so all implementation work is tied directly to the spec diff.
  • Mandatory end-of-run validation: Dispatches mode-appropriate reviewers (dual delta-coverage and substrate review for standard mode, cross-mirror review for extend mode) to verify implementation matches the design.
  • Use case: Use after a spec rewrite is approved to land implementation that exactly matches the new design, or to extend an existing concept with new changes while ensuring all related code sites are updated.

Quick Start

Use the implement-cohesively skill to drive implementation of the approved user authentication rewrite on the design/auth-rewrite branch, with automatic validation and cleanup of temporary scaffolding.

Frequently Asked Questions about implement-cohesively

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

FAQPage Schema
How do I ensure code implementation matches approved spec rewrites exactly?

Spec alignment during implementation is enforced by driving single-pass code, test, and CI changes that fulfill every promise in the spec diff. A mandatory end-of-run reviewer dispatch verifies that the codebase matches the locked design specification.

What is the best way to implement TDD workflow changes for large spec rewrites?

The best way to implement TDD workflow changes for large spec rewrites is to use diff-size budget gating. This ensures the implementation remains tied to the spec diff while automatic cleanup removes ephemeral scaffolding on successful completion.

When do I need to dispatch a cross-mirror review for spec compliance?

You need to dispatch a cross-mirror review for spec compliance when running in extend mode for post-rewrite-specs extension runs. Standard mode instead uses dual delta-coverage and substrate review to verify implementation matches the design.

Can I use this workflow to extend an existing design concept with new codebase changes?

Yes, you can use extend mode to extend an existing design concept with new codebase changes. This mode adapts input requirements and reviewer dispatch to ensure all related code sites are updated while maintaining full alignment with the locked design specification.

Why does my implementation drift from the approved design specification?

Implementation drifts from the approved design specification when code, test, and CI changes are not anchored to the spec diff. Composing with TDD-disciplined plan writing ensures all implementation work is tied directly to the locked design to prevent unapproved divergent changes.