comment-featurelisted

# comment-feature — bounded feature delivery through a comm Use this for a feature whose goal and acceptance are defined. Use `comment-spec` when a material goal or product fork still needs shaping; use `comment-prototype` when the human wants to see an exploratory change first. This skill composes `delivery-methodology`, `worklog`, `drive-plan`, `review-loop`, `steer`, and `ship`. Before using one, read its full `SKILL.md` (its `SKILL.md`). ## Project Root and identity Direct feature work uses its worklog as Project Root. When a Spec or existing Project Root URL is supplied, preserve it and make the worklog a child. A prototype promotion reuses and upgrades the existing worklog/branch. Keep the working Comment.io route and identity for every created artifact, edit, and comment. Invoke `comment-identity` only immediately before an uncredentialed direct-REST write. Never switch to an ambient registered or Botlets profile. ## Workflow 1. **Choose topology before editing.** Read `delivery-methodology` plus the repo's `AGENTS.md`/`CLAUDE.md` and linked delivery/testing docs. Record one: - direct task branch for a complete independently shippable change; or - controlled lift for foundational work with unsafe intermediate states. Feature flags require a clean bounded activation seam. Do not use them to preserve two architectures, dual writes, duplicated state, or broad compatibility scaffolding. 2. **Open or inherit one worklog.** Put the plan in its body