Skip to content

Question: how do you distinguish cc-sdd from nearby harness/meta-wrapper projects? #149

@hongsw

Description

@hongsw

Hi — I'm mapping the emerging harness/meta-wrapper / workflow layer around coding agents, and cc-sdd looks especially interesting because it appears to package a structured development methodology across multiple base agents.

I'm trying to understand how you would distinguish cc-sdd from nearby projects such as:

  • oh-my-claudecode
  • oh-my-openagent
  • oh-my-codex
  • oh-my-agent
  • everything-claude-code
  • claude-code-router

A few concrete questions:

  1. What is the clearest one-line positioning of cc-sdd today?
  2. Is it best understood as a methodology pack, workflow harness, team governance layer, agent wrapper, or something else?
  3. What should users expect from cc-sdd that they should not expect from the projects above?
  4. Is the main differentiator spec-driven structure, cross-runtime portability, or team workflow standardization?
  5. If someone is choosing among these tools, what decision rule would you give them?

The goal is to describe this category more precisely than just “another agent wrapper.”

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions