comment-devlisted

# comment-dev — the engineering front door One thing to talk to. Describe the work; `comment-dev` classifies the intent and routes to the path that fits, so you don't have to remember which `comment-*` skill to call. It is a thin **dispatcher** — it does no delivery itself; it picks a path and hands off. Every route follows the same startup bias: get the simplest useful change in front of real users, learn whether they love it, and add complexity only when evidence or a hard invariant requires it. > Not a Comment.io *document* skill. "Make me a comm / read this doc / edit this > comm" is the **`comment`** skill. `comment-dev` is for *building, fixing, and > shaping software*. ## Routing Classify the request, state which path you're taking and why (one line), then run that skill (read its full `SKILL.md` first — naming it here does not load it): | The request looks like… | Route to | Why | |---|---|---| | A rough/unshaped idea; goal, scope, or product fit unsettled; "should we…", "what if…", "scope this", "is this worth doing" | **`comment-spec`** | Shape it into a crisp spec first; it then invokes `comment-feature`. | | A defined feature; "build / add / implement / wire up X", clear what success is | **`comment-feature`** | Choose direct/lift topology → build bounded deltas → ship. | | A defect/regression; "X is broken", "this throws", "stopped working", "wrong output" | **`comment-bug`** | Reproduce → failing test → fix → verify. | | A fast, small, or exploratory chang