From bd43f4ea73ca766ee82e9e00e6b482c99a0c0cec Mon Sep 17 00:00:00 2001 From: nntrivi2001 Date: Tue, 25 Aug 2026 09:18:44 +0700 Subject: [PATCH] docs(claude): prefer ccam:ship-feature over raw superpowers skills for lane stage tracking --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index b362f5c4..9b0d35b7 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -75,3 +75,4 @@ See `docs/LANES.md` for full guide: stage reporting, custom templates, lane acti - Use project skills from `skills/` for repeatable workflows (they ship with the `ccam` plugin: `/ccam:`, or the bare `/` alias). - Use `agents/` subagents for focused review or investigation passes (they ship with the plugin: `ccam:backend-reviewer`, etc.). - **Declare lane stage even in plain chat, not just inside skills.** `ccam stage` (see `docs/LANES.md` § Reporting a stage) is a reporting command, not a skill-only ritual — any Claude session working inside an adopted lane's cwd should call it on real stage transitions (starting to plan, starting to implement, running tests, opening the PR, etc.), whether or not a skill is driving. Tool-event detection (`server/lib/stage-detect.js`) only ever paints the amber "detected" badge, never the blue `current` ring — a lane worked entirely through plain chat with no `ccam stage` calls will show a stale `current` stage no matter how much real work happens. Skip it only when `ccam stage` reports no lane owns the cwd (not adopted). +- **Prefer `ccam:ship-feature`(`-lane`) over invoking `superpowers:brainstorming`/`writing-plans`/`executing-plans`/`subagent-driven-development`/`test-driven-development` directly for implementation work inside a lane's cwd.** Those Superpowers skills know nothing about CCAM lanes and never call `ccam stage` themselves — going straight to them (skipping the CCAM wrapper) is exactly how a lane's `current` stage goes stale mid-implementation while `ccam stage` is never called for real transitions. `ccam:ship-feature`/`ship-feature-lane` drive the same underlying Superpowers skills phase-by-phase and declare `ccam stage` at every boundary — pick one of them first for any multi-phase feature/bugfix inside a lane; reach for a bare Superpowers skill directly only for work with no lane cwd to report against (e.g. a scratch repo, or explicitly told to skip the CCAM wrapper).