claude-fsd 1.3.6 → 1.3.8

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 CHANGED
@@ -162,16 +162,20 @@ if [ $# -eq 0 ]; then
162
162
  echo
163
163
  echo "# Project Brief" > BRIEF.md
164
164
  echo "" >> BRIEF.md
165
- echo "## Overview" >> BRIEF.md
166
- echo "Describe your project here..." >> BRIEF.md
165
+ echo "## Vision" >> BRIEF.md
166
+ echo "Describe the big picture vision and what you want to achieve..." >> BRIEF.md
167
167
  echo "" >> BRIEF.md
168
- echo "## Goals" >> BRIEF.md
169
- echo "- Goal 1" >> BRIEF.md
170
- echo "- Goal 2" >> BRIEF.md
168
+ echo "## Core Requirements" >> BRIEF.md
169
+ echo "- Core requirement 1" >> BRIEF.md
170
+ echo "- Core requirement 2" >> BRIEF.md
171
171
  echo "" >> BRIEF.md
172
- echo "## Requirements" >> BRIEF.md
173
- echo "- Requirement 1" >> BRIEF.md
174
- echo "- Requirement 2" >> BRIEF.md
172
+ echo "## Key Features" >> BRIEF.md
173
+ echo "- Feature 1" >> BRIEF.md
174
+ echo "- Feature 2" >> BRIEF.md
175
+ echo "" >> BRIEF.md
176
+ echo "## Success Criteria" >> BRIEF.md
177
+ echo "- Success criterion 1" >> BRIEF.md
178
+ echo "- Success criterion 2" >> BRIEF.md
175
179
 
176
180
  open_with_editor "BRIEF.md"
177
181
  echo
@@ -56,8 +56,8 @@ DO NOT answer the questions yourself - just generate them for the user to answer
56
56
  "
57
57
 
58
58
  # run BA's
59
- echo "Running claude..."
60
- claude --dangerously-skip-permissions -p "$prompt1" | tee >(cat > $LOGFILE-ba1)
59
+ echo "Running claude with opus model..."
60
+ claude --model opus --dangerously-skip-permissions -p "$prompt1" | tee >(cat > $LOGFILE-ba1)
61
61
 
62
62
  # Only run codex if available
63
63
  if command -v codex >/dev/null 2>&1; then
@@ -61,15 +61,15 @@ Use feature branches for development work. Follow YAGNI principle - don't over-e
61
61
  "
62
62
 
63
63
  # run BA's
64
- echo "Running claude..."
65
- claude --dangerously-skip-permissions -p "$prompt2" | tee >(cat > $LOGFILE-ba3-$round)
64
+ echo "Running claude with opus model..."
65
+ claude --model opus --dangerously-skip-permissions -p "$prompt2" | tee >(cat > $LOGFILE-ba3)
66
66
 
67
67
  # Only run codex if available
68
68
  if command -v codex >/dev/null 2>&1; then
69
69
  echo "Running codex o3 (results won't display)..."
70
- codex -m o3 --full-auto -q "$prompt2" > $LOGFILE-ba4-$round
70
+ codex -m o3 --full-auto -q "$prompt2" > $LOGFILE-ba4
71
71
  else
72
- echo "Codex not available, skipping o3 analysis" > $LOGFILE-ba4-$round
72
+ echo "Codex not available, skipping o3 analysis" > $LOGFILE-ba4
73
73
  fi
74
74
 
75
75
  echo -e "\033[32m==================================================================\033[0m"
package/bin/claudefsd-dev CHANGED
@@ -36,11 +36,13 @@ while true; do
36
36
  echo -e "\033[33m**** MEGATHINKING MODE ACTIVATED ****\033[0m"
37
37
  echo -e "\033[33mThis is your 4th development cycle. Taking a step back for architectural planning.\033[0m"
38
38
  MEGATHINKING_MODE="**** MEGATHINKING MODE ACTIVATED ****\nThis is your 4th development cycle. Before proceeding with the next task, please take a step back and use megathinking mode to architecturally plan the next phase of development. Consider the overall structure of the codebase, potential refactoring opportunities, design patterns, technical debt, and how the current work connects to broader project goals.\n\n"
39
+ CLAUDE_MODEL="opus"
39
40
  else
40
41
  MEGATHINKING_MODE=""
42
+ CLAUDE_MODEL="sonnet"
41
43
  fi
42
44
 
43
- time claude -p "
45
+ time claude --model $CLAUDE_MODEL -p "
44
46
  $MEGATHINKING_MODE
45
47
  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.
46
48
 
@@ -97,7 +99,7 @@ Please proceed with your analysis and task identification based on the project d
97
99
  fi
98
100
 
99
101
  # run the task
100
- time claude --dangerously-skip-permissions -p "
102
+ time claude --model $CLAUDE_MODEL --dangerously-skip-permissions -p "
101
103
  $MEGATHINKING_MODE
102
104
  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:
103
105
 
@@ -205,6 +207,8 @@ Look for typical 'cheating' patterns:
205
207
  Also note: please avoid switching git branches - stay on the current branch, as
206
208
  long as it's a proper feature branch.
207
209
 
210
+ If the task is complete, or there are a lot of pending changes, do a git commit.
211
+
208
212
  If the task is not complete, adjust the item in docs/PLAN.md with suggestions for
209
213
  the developer to complete the task properly.
210
214
 
@@ -220,7 +224,7 @@ If you have any ideas for the future, you can add them to IDEAS.md.
220
224
  echo -e "\033[32m==================================================================\033[0m"
221
225
 
222
226
  # run the reviewer/tester
223
- time claude --dangerously-skip-permissions -p "
227
+ time claude --model $CLAUDE_MODEL --dangerously-skip-permissions -p "
224
228
  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.
225
229
 
226
230
  Here is the task the developer has completed:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-fsd",
3
- "version": "1.3.6",
3
+ "version": "1.3.8",
4
4
  "description": "Claude Full Self Drive tools for autonomous AI-powered development",
5
5
  "bin": {
6
6
  "claude-fsd": "bin/claude-fsd",