claude-sprint-gate 1.1.0 → 1.2.0

package/ccsg.sh

@@ -101,13 +101,19 @@ build_mission_response() {
     [ -f "$f" ] && completed_count=$((completed_count + 1))
   done
 
+  # Read mission content for re-prompt
+  local mission_content=""
+  if [ -f "$MISSION_FILE" ]; then
+    mission_content=$(cat "$MISSION_FILE" | sed 's/\\/\\\\/g; s/"/\\"/g; s/$/\\n/' | tr -d '\n')
+  fi
+
   log "MISSION — next sprint: ${prefix}-v${next_ver} ($completed_count archived)"
 
   cat <<ENDJSON
 {
   "continue": false,
   "decision": "next_sprint",
-  "reason": "Sprint verified and complete. Mission is active.\\n\\nYour next action: create ${next_file}\\n\\n1. Read mission.md for your persona, objectives, and constraints\\n2. Review goals-completed/ to see what was delivered in prior sprints (${completed_count} archived files)\\n3. Define the next sprint goals that advance the mission\\n4. Write them as markdown checkboxes in ${next_file}\\n5. Start executing\\n\\nKeep working.",
+  "reason": "YOU CANNOT STOP. Sprint verified and complete. Mission is active.\\n\\nYOUR MISSION:\\n---\\n${mission_content}---\\n\\nYour next action: create ${next_file}\\n\\n1. Read goals-completed/ to see what was delivered in prior sprints (${completed_count} archived files)\\n2. Define the next sprint goals that advance the mission above\\n3. Write them as markdown checkboxes in ${next_file}\\n4. Start executing immediately\\n\\nDo not stop. Do not ask for confirmation. Create the sprint file and start working.",
   "next_sprint_file": "${next_file}",
   "next_version": ${next_ver},
   "mission_file": "mission.md",
@@ -201,8 +207,12 @@ ENDJSON
 
 # ── BLOCK: unchecked items remain ────────────────────────────────────
 if [ "$UNCHECKED" -gt 0 ]; then
-  WORK_ETHIC="WORK ETHIC: Compilation is not verification. Test each thing the way its end user would use it. A UI — open it in a browser, click every button, fill every form. An API — call it with real requests, check the actual responses. A CLI — run the commands, read the output. A pipeline — feed it real data, verify what comes out. Whatever it is, use it the way a customer would, not the way the developer who wrote it imagines it works. If you cannot show real output proving it works end-to-end, it is not done. Never trade correctness for speed."
-  build_block_response "$GOAL_FILE" "$WORK_ETHIC"
+  # Re-prompt: inject the full goal file so the agent gets the complete task back
+  GOAL_CONTENT=$(cat "$GOAL_FILE" | sed 's/\\/\\\\/g; s/"/\\"/g; s/$/\\n/' | tr -d '\n')
+
+  REPROMPT="YOU CANNOT STOP. ${UNCHECKED} of ${TOTAL} items in $(basename "$GOAL_FILE") are not done.\\n\\nRe-read the goal file and continue executing. Here is your active task:\\n\\n---\\n${GOAL_CONTENT}---\\n\\nWork through each unchecked item (- [ ]) in order. Check each one off (- [x]) as you complete it. Do not stop until every box is checked.\\n\\nWORK ETHIC: Compilation is not verification. Test each thing the way its end user would use it. A UI — open it in a browser, click every button, fill every form. An API — call it with real requests, check the actual responses. A CLI — run the commands, read the output. A pipeline — feed it real data, verify what comes out. Whatever it is, use it the way a customer would, not the way the developer who wrote it imagines it works. If you cannot show real output proving it works end-to-end, it is not done. Never trade correctness for speed."
+
+  build_block_response "$GOAL_FILE" "$REPROMPT"
   exit 0
 fi
 
@@ -335,5 +345,8 @@ TOTAL=$UNCHECKED
 
 # Block with the new verification sprint
 GOAL_FILE="$VERIFY_FILE"
-build_block_response "$VERIFY_FILE" "You just finished a sprint. But finishing code is not finishing the product. A verification sprint has been created at $(basename "$VERIFY_FILE"). Test each deliverable the way its end user would use it. If you cannot show real output proving it works end-to-end, it is not done."
+# Re-prompt with full verification sprint content
+VERIFY_CONTENT=$(cat "$VERIFY_FILE" | sed 's/\\/\\\\/g; s/"/\\"/g; s/$/\\n/' | tr -d '\n')
+VERIFY_REPROMPT="You just finished a sprint. But finishing code is not finishing the product. A verification sprint has been created. YOUR TASK NOW:\\n\\n---\\n${VERIFY_CONTENT}---\\n\\nWork through each unchecked item. Do not stop until every box is checked."
+build_block_response "$VERIFY_FILE" "$VERIFY_REPROMPT"
 exit 0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-sprint-gate",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Claude Code Sprint Gate — sprint lifecycle manager with verification gates",
   "bin": {
     "ccsg": "bin/ccsg.js"

package/test-ccsg.sh

@@ -500,7 +500,7 @@ assert_contains "blocks stop (mission active)" '"continue": false' "$OUTPUT"
 assert_contains "decision is next_sprint" '"next_sprint"' "$OUTPUT"
 assert_contains "suggests v2" 'v2' "$OUTPUT"
 assert_contains "references mission.md" 'mission.md' "$OUTPUT"
-assert_contains "tells agent to keep working" 'Keep working' "$OUTPUT"
+assert_contains "tells agent to keep working" 'Do not stop' "$OUTPUT"
 assert_file_exists "verify moved to completed" "$GOALS_COMPLETED/goal-product-v1-verify.md"
 assert_file_not_exists "verify removed from open" "$GOALS_OPEN/goal-product-v1-verify.md"
 assert_json_valid "valid JSON" "$OUTPUT"