claude-fsd 1.3.14 → 1.3.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/claudefsd-dev +39 -8
- package/package.json +1 -1
package/bin/claudefsd-dev
CHANGED
|
@@ -42,7 +42,8 @@ while true; do
|
|
|
42
42
|
CLAUDE_MODEL="sonnet"
|
|
43
43
|
fi
|
|
44
44
|
|
|
45
|
-
|
|
45
|
+
# Define the planner prompt
|
|
46
|
+
PLANNER_PROMPT="
|
|
46
47
|
$MEGATHINKING_MODE
|
|
47
48
|
You are an AI assistant specialized in project management and software development workflows. Your task is to analyze project documentation and identify the next open task for a developer to work on.
|
|
48
49
|
|
|
@@ -84,7 +85,17 @@ Example output structure:
|
|
|
84
85
|
|
|
85
86
|
Please proceed with your analysis and task identification based on the project documentation. Your final output should consist only of the task description in <task_description> tags or <ALL DONE>, and should not duplicate or rehash any of the work you did in the analysis section.
|
|
86
87
|
|
|
87
|
-
"
|
|
88
|
+
"
|
|
89
|
+
|
|
90
|
+
# Save the prompt to the log file first
|
|
91
|
+
echo "=== PROMPT ===" > $LOGFILE-planner
|
|
92
|
+
echo "$PLANNER_PROMPT" >> $LOGFILE-planner
|
|
93
|
+
echo "=== END PROMPT ===" >> $LOGFILE-planner
|
|
94
|
+
echo "" >> $LOGFILE-planner
|
|
95
|
+
echo "=== OUTPUT ===" >> $LOGFILE-planner
|
|
96
|
+
|
|
97
|
+
# Run claude and append output to the log file
|
|
98
|
+
time claude --model $CLAUDE_MODEL --dangerously-skip-permissions -p "$PLANNER_PROMPT" 2>&1 | tee -a $LOGFILE-planner
|
|
88
99
|
|
|
89
100
|
nexttask=$(cat $LOGFILE-planner)
|
|
90
101
|
|
|
@@ -98,8 +109,8 @@ Please proceed with your analysis and task identification based on the project d
|
|
|
98
109
|
echo -e "\033[33mThis is your 4th development cycle. Taking a step back for architectural planning.\033[0m"
|
|
99
110
|
fi
|
|
100
111
|
|
|
101
|
-
#
|
|
102
|
-
|
|
112
|
+
# Define the developer prompt
|
|
113
|
+
DEVELOPER_PROMPT="
|
|
103
114
|
$MEGATHINKING_MODE
|
|
104
115
|
You are an AI developer working within an automated development environment. Your role is to complete tasks, plan implementations, and maintain high-quality code. Here is the specific task you need to complete:
|
|
105
116
|
|
|
@@ -177,7 +188,17 @@ Your final output should follow this structure:
|
|
|
177
188
|
Remember to adhere to the project's standards and best practices. Your work will be reviewed before being committed to the repository.
|
|
178
189
|
|
|
179
190
|
Your final output should consist only of the execution details, linter output, changes description, questions update, and ideas update. Do not duplicate or rehash any of the work you did in the implementation planning section.
|
|
180
|
-
"
|
|
191
|
+
"
|
|
192
|
+
|
|
193
|
+
# Save the prompt to the log file first
|
|
194
|
+
echo "=== PROMPT ===" > $LOGFILE-developer
|
|
195
|
+
echo "$DEVELOPER_PROMPT" >> $LOGFILE-developer
|
|
196
|
+
echo "=== END PROMPT ===" >> $LOGFILE-developer
|
|
197
|
+
echo "" >> $LOGFILE-developer
|
|
198
|
+
echo "=== OUTPUT ===" >> $LOGFILE-developer
|
|
199
|
+
|
|
200
|
+
# Run claude and append output to the log file
|
|
201
|
+
time claude --model $CLAUDE_MODEL --dangerously-skip-permissions -p "$DEVELOPER_PROMPT" | tee -a $LOGFILE-developer
|
|
181
202
|
|
|
182
203
|
echo -e "\033[32m==================================================================\033[0m"
|
|
183
204
|
echo -e "\033[32m== REVIEWING WORK (backgrounded)\033[0m"
|
|
@@ -229,8 +250,8 @@ If you have any ideas for the future, you can add them to IDEAS.md.
|
|
|
229
250
|
echo -e "\033[32m== REVIEWING/TESTING/COMMITTING WORK\033[0m"
|
|
230
251
|
echo -e "\033[32m==================================================================\033[0m"
|
|
231
252
|
|
|
232
|
-
#
|
|
233
|
-
|
|
253
|
+
# Define the reviewer/tester prompt
|
|
254
|
+
REVIEWER_PROMPT="
|
|
234
255
|
You are an expert megathinker static code reviewer tasked with thoroughly examining a developer's work on a specific task. Your goal is to ensure the task is complete and meets high-quality standards.
|
|
235
256
|
|
|
236
257
|
Here is the task the developer has completed:
|
|
@@ -307,7 +328,17 @@ Actions Taken:
|
|
|
307
328
|
</review_summary>
|
|
308
329
|
|
|
309
330
|
Please proceed with your thorough code review and analysis. Your final output should consist only of the review summary and should not duplicate or rehash any of the work you did in the thinking block.
|
|
310
|
-
"
|
|
331
|
+
"
|
|
332
|
+
|
|
333
|
+
# Save the prompt to the log file first
|
|
334
|
+
echo "=== PROMPT ===" > $LOGFILE-tester
|
|
335
|
+
echo "$REVIEWER_PROMPT" >> $LOGFILE-tester
|
|
336
|
+
echo "=== END PROMPT ===" >> $LOGFILE-tester
|
|
337
|
+
echo "" >> $LOGFILE-tester
|
|
338
|
+
echo "=== OUTPUT ===" >> $LOGFILE-tester
|
|
339
|
+
|
|
340
|
+
# Run claude and append output to the log file
|
|
341
|
+
time claude --model $CLAUDE_MODEL --dangerously-skip-permissions -p "$REVIEWER_PROMPT" | tee -a $LOGFILE-tester
|
|
311
342
|
|
|
312
343
|
# Check if verifier has confirmed all tasks are truly complete
|
|
313
344
|
set +e
|