Skip to content

sno-ai/sno-station-skills / skills/T-delegation-and-work-orders/pl/skills/pl

MANUAL-ONLY — load solely when the human owner types `/pl`, uses `$pl`, or asks you to act as the Project Lead (PL). Supervise one project lane and its executor agents. A charter or dispatch means: you are an EXECUTOR, not the PL.

FileKindSize
SKILL.mdskill md61.7 KB
references/callsigns.txtmarkdown384 B
references/decision-rights.mdmarkdown4.8 KB
references/dispatch-template.mdmarkdown38.2 KB
references/pocket-card.mdmarkdown1.9 KB
references/progress-reporting-hooks.mdmarkdown2.3 KB
references/todo-template.mdmarkdown6.9 KB
scripts/agent-cli-help.tother1.2 KB
scripts/attempt-gate.shexecutablescript3.6 KB
scripts/attempt-gate.tother4.6 KB
scripts/callsign-transfer-e2e.shexecutablescript7.9 KB
scripts/callsign-worktree.tother1.7 KB
scripts/callsign.shexecutablescript15.2 KB
scripts/convergence-watch.shexecutablescript8.6 KB
scripts/core-structure.tother5.7 KB
scripts/docker-env-doctor.shexecutablescript19.4 KB
scripts/exec-sentinel.shexecutablescript5.8 KB
scripts/exec-sentinel.tother2.4 KB
scripts/exec-state.shexecutablescript20.8 KB
scripts/exec-state.tother23.1 KB
scripts/exec-trust.shscript5.3 KB
scripts/exec-trust.tother6.4 KB
scripts/executor-wall.shexecutablescript6.8 KB
scripts/executor-wall.texecutablescript9.5 KB
scripts/fence-check.shexecutablescript4.4 KB
scripts/general-env-doctor.shexecutablescript14.0 KB
scripts/general-env-doctor.tother5.8 KB
scripts/gpu-watch.shexecutablescript4.5 KB
scripts/gpu-watch.tother1.5 KB
scripts/lane-open.shexecutablescript4.1 KB
scripts/lane-open.tother3.9 KB
scripts/lane-resolve.shexecutablescript5.0 KB
scripts/lane-resolve.texecutablescript7.0 KB
scripts/log-watch.shexecutablescript10.9 KB
scripts/log-watch.texecutablescript6.8 KB
scripts/on-station-proof.texecutablescript1.9 KB
scripts/portable-paths.tother1.5 KB
scripts/roster-git.tother4.1 KB
scripts/roster-reach.tother2.8 KB
scripts/roster.shexecutablescript19.9 KB
scripts/script-running.shscript5.8 KB
scripts/script-running.tother3.7 KB
scripts/selftest/run-selftest.shexecutablescript1.2 KB
scripts/spawn-exec-generation-e2e.shexecutablescript1.9 KB
scripts/spawn-exec-help.tother2.8 KB
scripts/spawn-exec-interactive-e2e.shscript13.2 KB
scripts/spawn-exec-lane-resolve.tother3.5 KB
scripts/spawn-exec-mission-state-e2e.shscript1.8 KB
scripts/spawn-exec-on-station-e2e.shexecutablescript2.2 KB
scripts/spawn-exec-operate.tother9.4 KB
scripts/spawn-exec.shexecutablescript36.8 KB
scripts/todo-close-evidence.tother1.2 KB
scripts/todo.shexecutablescript35.5 KB
scripts/todo.tother27.9 KB

scripts/script-running.t

View on GitHub
#!/usr/bin/env bash
# script-running.sh — a process is what it IS, never what its command line mentions.
#
# A checker can match itself, and an executor charter can name a script without
# running it. Both are false positives when matching the whole command line.
set -Eeuo pipefail

CHECK="${CHECK:-$(dirname "$0")/script-running.sh}"

root="$(mktemp -d)"
pids=()
cleanup() {
  for p in ${pids[@]+"${pids[@]}"}; do kill "$p" 2>/dev/null || true; done
  rm -rf -- "$root"
}
trap cleanup EXIT

tests=0
failures=0
check() { # $1 label, rest: command
  local label="$1"; shift
  tests=$((tests + 1))
  if "$@"; then printf 'ok %d - %s\n' "$tests" "$label"
  else printf 'not ok %d - %s\n' "$tests" "$label"; failures=$((failures + 1)); fi
}

run_check() { bash "$CHECK" "$@" >/dev/null 2>&1; }
not_running() { ! bash "$CHECK" "$@" >/dev/null 2>&1; }
exits_with() { # $1 expected code, rest: args to the checker
  local want="$1"; shift
  local got=0
  bash "$CHECK" "$@" >/dev/null 2>&1 || got=$?
  [ "$got" = "$want" ]
}
pid_absent() { # $1 pid, rest: args to the checker
  local pid="$1"; shift
  local out
  out="$(bash "$CHECK" "$@" 2>/dev/null || true)"
  case " $out " in
    *" $pid "*) return 1 ;;
    *) return 0 ;;
  esac
}

# Two scripts: the one we look for, and an unrelated one used to carry contaminating text.
victim="$root/victim.sh"
other="$root/other.sh"
printf '#!/usr/bin/env bash\nsleep 30\n' > "$victim"
printf '#!/usr/bin/env bash\nsleep 30\n' > "$other"
chmod +x "$victim" "$other"

# 1. an honest negative first, before anything exists that could produce a false positive
check "reports not running when nothing is" not_running victim.sh
check "not running is exit 1" exits_with 1 victim.sh

# 2-4. interpreter form: `bash /path/victim.sh --log X` — argv[0]=bash, argv[1]=the script
bash "$victim" --log "$root/a.log" &
pids+=($!)
sleep 0.3
check "finds it when launched through an interpreter" run_check victim.sh
check "--arg narrows to the right run" run_check victim.sh --arg "$root/a.log"
check "--arg rejects a run with a different argument" not_running victim.sh --arg /nowhere/b.log

# 5. Self-mention: a shell whose own command line mentions the script name.
#    `pgrep -f victim.sh` matches this process. Position-matching must not.
bash -c 'sleep 30 # victim.sh --log /tmp/x' &
mention_pid=$!
pids+=("$mention_pid")
sleep 0.3
check "a shell that merely mentions the name is not counted" \
  pid_absent "$mention_pid" victim.sh

# 6. Charter text: a different script carrying the name inside one of its arguments,
#    the exact shape of an executor charter naming the command it chartered.
bash "$other" "mission: run the gate · command: $victim --log $root/a.log" &
charter_pid=$!
pids+=("$charter_pid")
sleep 0.3
check "a different script carrying the name in an argument is not counted" \
  pid_absent "$charter_pid" victim.sh
check "and it is still not counted when --arg matches the carried text" \
  pid_absent "$charter_pid" victim.sh --arg "$root/a.log"

# 7. direct form: argv[0] IS the script, because it was run through its shebang
"$victim" --log "$root/c.log" &
pids+=($!)
sleep 0.3
check "finds it when run directly through its shebang" run_check victim.sh --arg "$root/c.log"

# 8. usage
check "no script name is a usage error" exits_with 2
check "an unknown flag is a usage error" exits_with 2 victim.sh --nope
check "--arg with no value is a usage error" exits_with 2 victim.sh --arg
check "--help exits 0" run_check --help

# 9. the checker never counts itself, even when it is the script being asked about
check "the checker does not match its own process" exits_with 1 script-running.sh

printf '1..%d\n' "$tests"
if [ "$failures" -gt 0 ]; then
  printf '# %d of %d failed\n' "$failures" "$tests" >&2
  exit 1
fi
printf '# all %d passed\n' "$tests"
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall