4 Commits
Author SHA1 Message Date
Vipul Gupta (@vipulgupta2048)andCommandCodeBot e8089ebe61 docs: add Command Code as a native skills provider
Command Code has a native skills CLI (cmd skills add <owner/repo>) that
clones the repo, discovers every SKILL.md, and installs into
.commandcode/skills/ — no plugin manifest or copied files needed.

- README: add Command Code install block
- docs/commandcode-setup.md: setup guide (install/manage/usage, paths)
- docs/comparison.md: add Command Code to tooling reach

Verified end-to-end against addyosmani/agent-skills: add (all / -s / @branch /
path / --global / --force), list (+ -d), and remove (project / --global) via
the CLI, plus skill discovery in the TUI slash menu.

Signed-off-by: Vipul Gupta (@vipulgupta2048) <vipulgupta2048@gmail.com>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Signed-off-by: Vipul Gupta (@vipulgupta2048) <vipulgupta2048@gmail.com>
2026-08-02 23:54:39 +05:30
Addy Osmani 7ce442de03 docs(comparison): refresh and expand the three-way comparison
Bring docs/comparison.md up to date and make it more useful for people
choosing between the packs:

- agent-skills: add the three-tier eval framework as the current point of
  difference, plus current tooling (Codex, Kiro, the npx skills CLI),
  /build auto, and the 24-skill / 7-checklist / Definition-of-Done facts.
- Superpowers: correct to ~14 inner-loop skills, the consolidated single
  task reviewer, the worst-case-executor plan standard, and its main
  unmet ask (agent teams); drop the stale Gemini reference.
- Matt Pocock's skills: reframe around the grilling primitive and the
  grown ~30-skill toolkit (in-progress/deprecated dirs, wayfinder,
  seam-based TDD), not a "tight set".
- Add a much fuller "How to decide what to use" section after the table:
  by shape of work, by what you optimize for, concrete scenarios, solo
  vs team, and an honest shared-frontier note on cross-session memory.

Keeps the fair-not-flattering stance and the Om Mishra head-to-head.
2026-07-10 10:01:07 -07:00
Addy Osmani 8fea8b42c1 docs(comparison): caution against stacking multiple routers
Per review feedback: clarify that cherry-picking individual skills works,
but running two frameworks as active routers at once causes command-name
conflicts, competing routing, and clashing TDD philosophies. Recommend
one primary router + à la carte borrowing.
2026-06-20 15:35:10 -07:00
Addy Osmani 176c6fa130 [docs] Add comparison to alternatives 2026-06-20 15:03:06 -07:00