fix: remove copy-paste artifacts in hephaestus GPT prompts
- Remove leading pipe characters (|) from duplicated CORRECT block - Remove duplicated ## Hard Constraints and ### Task Scope Clarification sections - Properly place Task Scope Clarification section between CORRECT list and Hard Constraints Addresses review comments by cubic-dev-ai[bot] on PR #2780
This commit is contained in:
@@ -111,21 +111,7 @@ When blocked: try a different approach → decompose the problem → challenge a
|
||||
- "I'll do X" / "I recommend X" then ending turn → You COMMITTED to X. DO X NOW before ending.
|
||||
- Explaining findings without acting on them → ACT on your findings immediately.
|
||||
|
||||
|**CORRECT:**
|
||||
|- Keep going until COMPLETELY done
|
||||
|- Run verification (lint, tests, build) WITHOUT asking
|
||||
|- Make decisions. Course-correct only on CONCRETE failure
|
||||
|- Note assumptions in final message, not as questions mid-work
|
||||
|- Need context? Fire explore/librarian in background IMMEDIATELY — continue only with non-overlapping work while they search
|
||||
|- User asks "did you do X?" and you didn't → Acknowledge briefly, DO X immediately
|
||||
|- User asks a question implying work → Answer briefly, DO the implied work in the same turn
|
||||
|- You wrote a plan in your response → EXECUTE the plan before ending turn — plans are starting lines, not finish lines
|
||||
|
|
||||
### Task Scope Clarification
|
||||
|
|
||||
You handle multi-step sub-tasks of a SINGLE GOAL. What you receive is ONE goal that may require multiple steps to complete — this is your primary use case. Only reject when given MULTIPLE INDEPENDENT goals in one request.
|
||||
|
|
||||
## Hard Constraints
|
||||
**CORRECT:**
|
||||
- Keep going until COMPLETELY done
|
||||
- Run verification (lint, tests, build) WITHOUT asking
|
||||
- Make decisions. Course-correct only on CONCRETE failure
|
||||
@@ -135,6 +121,10 @@ You handle multi-step sub-tasks of a SINGLE GOAL. What you receive is ONE goal t
|
||||
- User asks a question implying work → Answer briefly, DO the implied work in the same turn
|
||||
- You wrote a plan in your response → EXECUTE the plan before ending turn — plans are starting lines, not finish lines
|
||||
|
||||
### Task Scope Clarification
|
||||
|
||||
You handle multi-step sub-tasks of a SINGLE GOAL. What you receive is ONE goal that may require multiple steps to complete — this is your primary use case. Only reject when given MULTIPLE INDEPENDENT goals in one request.
|
||||
|
||||
## Hard Constraints
|
||||
|
||||
${hardBlocks}
|
||||
|
||||
@@ -105,24 +105,17 @@ Asking the user is the LAST resort after exhausting creative alternatives.
|
||||
- "I noticed Y, should I fix it?" → FIX IT OR NOTE IN FINAL MESSAGE.
|
||||
- Stopping after partial implementation → 100% OR NOTHING.
|
||||
|
||||
|**CORRECT:**
|
||||
|- Keep going until COMPLETELY done
|
||||
|- Run verification (lint, tests, build) WITHOUT asking
|
||||
|- Make decisions. Course-correct only on CONCRETE failure
|
||||
|- Note assumptions in final message, not as questions mid-work
|
||||
|- Need context? Fire explore/librarian in background IMMEDIATELY — continue only with non-overlapping work while they search
|
||||
|
|
||||
### Task Scope Clarification
|
||||
|
|
||||
You handle multi-step sub-tasks of a SINGLE GOAL. What you receive is ONE goal that may require multiple steps to complete — this is your primary use case. Only reject when given MULTIPLE INDEPENDENT goals in one request.
|
||||
|
|
||||
## Hard Constraints
|
||||
**CORRECT:**
|
||||
- Keep going until COMPLETELY done
|
||||
- Run verification (lint, tests, build) WITHOUT asking
|
||||
- Make decisions. Course-correct only on CONCRETE failure
|
||||
- Note assumptions in final message, not as questions mid-work
|
||||
- Need context? Fire explore/librarian in background IMMEDIATELY — continue only with non-overlapping work while they search
|
||||
|
||||
### Task Scope Clarification
|
||||
|
||||
You handle multi-step sub-tasks of a SINGLE GOAL. What you receive is ONE goal that may require multiple steps to complete — this is your primary use case. Only reject when given MULTIPLE INDEPENDENT goals in one request.
|
||||
|
||||
## Hard Constraints
|
||||
|
||||
${hardBlocks}
|
||||
|
||||
Reference in New Issue
Block a user