scripts/task-start

skills/executing-plans/scripts/task-start · 1.2 KB · View on GitHub at 22f0b46

About this file (written at import)

What it does. Bash script that takes a plan file and a task number, runs subagent-driven-development’s task-brief to write that task’s text to a brief file in the plan’s workspace, and prints the brief path and the current commit as BASE. It refuses to run outside a git working tree with at least one commit.

Why it’s here. SKILL.md’s task loop says to “Run this skill’s scripts/task-start PLAN_FILE N by its absolute path” at the start of each task. It combines two steps into one call because, as its comments say, every tool call in an inline session re-reads the whole context.

scripts/task-start

#!/usr/bin/env bash
# Begin one task of an inline plan execution in a single call: extract the
# task's brief (via subagent-driven-development's task-brief, so both skills
# share one workspace) and record BASE, the commit the task's review range is
# cut from. One tool call instead of two, because every call in an inline
# session is a turn that re-reads the whole context.
#
# Usage: task-start PLAN_FILE TASK_NUMBER
# Prints:
#   brief: <path to the task's brief file>
#   base:  <full SHA of HEAD>
set -euo pipefail

if [ $# -ne 2 ]; then
  echo "usage: task-start PLAN_FILE TASK_NUMBER" >&2
  exit 2
fi

plan=$1
n=$2
sdd="$(cd "$(dirname "$0")/../../subagent-driven-development/scripts" && pwd)"

# BASE comes from the same repository the brief is written into (sdd-repo
# also refuses one with no commit yet), not from the bare cwd.
repo=$("${BASH:-bash}" "$sdd/sdd-repo" --with-commit)
out=$("$sdd/task-brief" "$plan" "$n")
brief=$(printf '%s\n' "$out" | sed -n 's/^wrote \(.*\): [0-9][0-9]* lines$/\1/p')
[ -n "$brief" ] || { echo "task-brief did not report a path: $out" >&2; exit 1; }
base=$(git -C "$repo" rev-parse --verify HEAD)

echo "brief: $brief"
echo "base: $base"