ralph-teams 1.0.20 → 1.0.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ralph-teams",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "description": "CLI tool for Ralph Teams",
   "bin": {
     "ralph-teams": "dist/index.js",

package/prompts/team-lead-policy.md

@@ -14,8 +14,9 @@ You coordinate epic execution. Do not write implementation code yourself.
 ## Epic Planning
 
 - If `epicPlanning.enabled = 0`, do not spawn an epic planner. Use the epic as provided.
+- If a usable canonical plan file already exists at the path provided in the prompt, do not spawn the epic planner. Use that plan even if `planned` is still `false`.
 - If the epic is already marked `planned=true`, do not spawn the epic planner. Read the canonical plan file path provided in the prompt and follow it.
-- Otherwise, if `epicPlanning.enabled = 1`, spawn the epic planner for any medium- or high-complexity epic.
+- Otherwise, if `epicPlanning.enabled = 1`, spawn the epic planner for any medium- or high-complexity epic that does not already have a usable canonical plan.
 - Only skip epic planning for clearly low-complexity epics where the acceptance criteria can be implemented literally with no meaningful design decisions.
 - When delegating epic planning, explicitly tell the epic planner the exact output path for the epic plan file and require it to write the plan there before replying.
 - Treat an epic planner response as incomplete if it only pastes or summarizes the plan in chat. The epic planner must perform the file write itself and only then report completion.

package/ralph.sh

@@ -133,9 +133,13 @@ resolve_rjq_bin() {
     fi
   done
 
-  if command -v rjq >/dev/null 2>&1; then
-    command -v rjq
-    return 0
+  if type -P rjq >/dev/null 2>&1; then
+    local path_rjq
+    path_rjq="$(type -P rjq)"
+    if [ -n "$path_rjq" ] && [ -e "$path_rjq" ] && [ -x "$path_rjq" ]; then
+      echo "$path_rjq"
+      return 0
+    fi
   fi
 
   return 1
@@ -144,14 +148,12 @@ resolve_rjq_bin() {
 RJQ_BIN="$(resolve_rjq_bin || true)"
 
 rjq() {
-  if [ -z "${RJQ_BIN:-}" ]; then
-    echo "Error: rjq binary is not configured." >&2
-    exit 1
-  fi
-
-  if [ ! -e "$RJQ_BIN" ]; then
-    echo "Error: resolved rjq binary does not exist: $RJQ_BIN" >&2
-    exit 1
+  if [ -z "${RJQ_BIN:-}" ] || [ ! -e "$RJQ_BIN" ]; then
+    RJQ_BIN="$(resolve_rjq_bin || true)"
+    if [ -z "${RJQ_BIN:-}" ] || [ ! -e "$RJQ_BIN" ]; then
+      echo "Error: resolved rjq binary does not exist: ${RJQ_BIN:-<unset>}" >&2
+      exit 1
+    fi
   fi
 
   case "$RJQ_BIN" in
@@ -1223,6 +1225,8 @@ spawn_epic_bg() {
   EPIC_TITLE=$(rjq read "$PRD_FILE" ".epics[$EPIC_INDEX].title")
   local EPIC_JSON
   EPIC_JSON=$(rjq read "$PRD_FILE" ".epics[$EPIC_INDEX]")
+  local EPIC_PLANNED
+  EPIC_PLANNED=$(rjq read "$PRD_FILE" ".epics[$EPIC_INDEX].planned" "false")
   local PENDING_STORIES_JSON
   PENDING_STORIES_JSON=$(rjq read "$PRD_FILE" ".epics[$EPIC_INDEX].userStories" | \
     node -e 'const fs=require("fs"); const stories=JSON.parse(fs.readFileSync(0,"utf8")); process.stdout.write(JSON.stringify(stories.filter(s => s.passes !== true)));')
@@ -1238,6 +1242,10 @@ spawn_epic_bg() {
   local WORKTREE_PRD_PATH="${WORKTREE_ABS_PATH}/${PRD_REL_PATH}"
   local WORKTREE_STATE_FILE="${WORKTREE_ABS_PATH}/${RALPH_RUNTIME_DIRNAME}/state/${EPIC_ID}.json"
   local WORKTREE_PLAN_FILE="${WORKTREE_ABS_PATH}/${RALPH_RUNTIME_DIRNAME}/plans/plan-${EPIC_ID}.md"
+  local WORKTREE_PLAN_EXISTS="false"
+  if [ -f "$WORKTREE_PLAN_FILE" ]; then
+    WORKTREE_PLAN_EXISTS="true"
+  fi
 
   init_epic_state_file "$EPIC_ID" "$EPIC_INDEX"
 
@@ -1268,6 +1276,12 @@ $EPIC_JSON
 If this epic has planned=true in the PRD, the canonical implementation plan is:
 $WORKTREE_PLAN_FILE
 
+## Planning Status
+- epic.planned = ${EPIC_PLANNED}
+- canonical_plan.exists = ${WORKTREE_PLAN_EXISTS}
+- If a usable canonical plan already exists, do NOT spawn the epic planner. Use it even if epic.planned is false.
+- Only spawn the epic planner when epicPlanning.enabled = 1 and there is no usable canonical plan for this epic.
+
 ## Stories To Plan And Execute
 Only these stories should be planned or worked in this run. Stories omitted here are already passed and must be treated as done context only.
 $PENDING_STORIES_JSON
@@ -1322,6 +1336,7 @@ $TEAM_LEAD_POLICY
 - Use the exact epic state file path shown above for every story update. The PRD path is read-only context.
 - If your runtime supports named sub-agents, use the dedicated story-planner, epic-planner, builder, story-validator, and epic-validator roles and choose their models using the policy above.
 - If a story fails validation and still has retries left, spawn a new Builder for the retry instead of reusing the previous Builder run.
+- If your runtime is Codex exec mode, `request_user_input` is unavailable. Never call it. Do not stop to ask the user questions. Make a reasonable assumption, continue, and report the assumption in your final summary only if it matters.
 
 Begin."
 
@@ -1549,7 +1564,7 @@ run_backend_agent_session() {
       local prompt_file="${SCRIPT_DIR}/prompts/agents/${agent_name}.md"
       local role_body
       role_body="$(extract_prompt_body "$prompt_file")"
-      printf '%s\n\n## Assignment\n%s\n' "$role_body" "$prompt" | codex \
+      printf 'Runtime note: This Codex session runs in exec mode. `request_user_input` is unavailable. Never call it. Do not stop to ask the user questions. Make a reasonable assumption and continue.\n\n%s\n\n## Assignment\n%s\n' "$role_body" "$prompt" | codex \
         -a never \
         exec \
         -C "$workdir" \