Pipeline Plan inline

Plan complete and saved to docs/plans/2026-03-02-ping-command.md.

---

Summary

The plan adds the shipwright ping command in 4 files, 9 tasks:

#	Task	File(s)
1-2	Create + chmod sw-ping.sh	scripts/sw-ping.sh (new)
3-4	Create + chmod sw-ping-test.sh	scripts/sw-ping-test.sh (new)
5	Run test in isolation — verify 6 PASS	—
6	Register ping) case in router	scripts/sw
7	Add test to npm test chain	package.json
8	Smoke-test via router	—
9	Commit	—

Key decisions:

• Standalone script (not inline in router) — only approach consistent with all 100+ existing commands, independently testable
• 6 tests matching sw-hello-test.sh exactly: output match, exit code, --help, -h, --version, invalid option
• ((PASS++)) pattern used throughout — proven safe on bash 3.2 under pipefail
• Router insertion goes immediately before *) wildcard at line ~608 of scripts/sw

---

Two execution options:

1. Subagent-Driven (this session) — I dispatch a fresh subagent per task, review between tasks, fast iteration with superpowers:subagent-driven-development

2. Parallel Session (separate) — Open a new session in this worktree and use superpowers:executing-plans for batch execution with checkpoints

Which approach would you like?