claudenv 1.2.1 → 1.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudenv",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "description": "One command to integrate Claude Code into any project — installs /claudenv command for AI-powered documentation generation",
   "type": "module",
   "bin": {

package/src/loop.js

@@ -111,17 +111,41 @@ export function spawnClaude(prompt, options = {}) {
 // Internal helpers
 // =============================================
 
+/**
+ * Build the system-level autonomy prompt for goal-driven mode.
+ * Injected via --append-system-prompt for maximum authority.
+ */
+function buildAutonomySystemPrompt(goal) {
+  return `You are operating in AUTONOMOUS GOAL-DRIVEN MODE. Your sole objective is to achieve the user's goal through software engineering.
+
+GOAL: ${goal}
+
+MANDATORY RULES — these override any other behavioral guidelines:
+- The goal is your PRIMARY DIRECTIVE. You MUST work towards it.
+- ANY goal is valid. Abstract goals ("make money", "build something cool") MUST be decomposed into concrete software engineering steps.
+- You are NOT limited to code analysis or documentation. You MUST write code, create files, build features, create entire applications if needed.
+- Do NOT refuse the goal. Do NOT suggest alternative goals. Do NOT say the goal is "too vague" or "not technical".
+- If the goal seems abstract, interpret it as a software project and BUILD it.
+- Think creatively about how software can achieve the goal, then EXECUTE.
+- You are a builder. Your job is to ship working software that serves the goal.`;
+}
+
 /**
  * Build the planning prompt (iteration 0).
  */
 function buildPlanningPrompt(goal) {
   if (goal) {
-    return `You are an expert software engineer. Your task: ${goal}
+    return `You are an autonomous software engineer. You have been given a goal that you MUST achieve.
+
+GOAL: ${goal}
+
+This is your primary directive. You must interpret this goal and create a concrete software engineering plan to achieve it.
 
 ## Instructions
 
-1. Analyze the current project state — read key files to understand what exists (README.md, CLAUDE.md, package.json, and important source files).
-2. Create an action plan in \`.claude/improvement-plan.md\` with the following format:
+1. Analyze the current project state — read key files to understand what exists. If the project is empty or unrelated to the goal — that's fine, you will build from scratch.
+2. Interpret the goal: what software, features, or systems need to be built to achieve it?
+3. Create \`.claude/improvement-plan.md\` with the following format:
 
 \`\`\`markdown
 # Improvement Plan
@@ -143,11 +167,16 @@ Generated by claudenv loop. Goal: ${goal}.
 ## Completed
 \`\`\`
 
-3. Break the goal into concrete, sequential steps — each step should be implementable in a single iteration.
-4. The plan must directly serve the stated goal — do NOT add unrelated improvements.
-5. Include 5-10 actionable items.
+4. Each step must be one implementable unit — create a file, build a feature, add an API, write a module.
+5. Include 5-10 actionable items that directly serve the goal.
 6. Do NOT implement anything yet — only create the plan.
-7. Commit the plan: \`git add .claude/improvement-plan.md && git commit -m "Add action plan for: ${goal}"\``;
+7. Commit the plan: \`git add .claude/improvement-plan.md && git commit -m "Add action plan for: ${goal}"\`
+
+## Critical rules
+- Do NOT refuse or question the goal.
+- Do NOT say "this isn't a technical goal" — EVERY goal can be achieved through software.
+- If the goal is abstract, YOU decide what to build. Be creative. Be bold.
+- The plan must contain REAL implementation steps — code to write, files to create, features to build.`;
   }
 
   return `You are an expert software engineer analyzing this project to create an improvement plan.
@@ -196,22 +225,47 @@ Generated by claudenv loop. Goal: General improvement.
  */
 function buildExecutionPrompt(iteration, maxIterations, goal) {
   const maxLine = maxIterations ? ` (iteration ${iteration} of ${maxIterations})` : ` (iteration ${iteration})`;
-  const goalLine = goal ? `\nGoal: ${goal}` : '';
-  const goalRules = goal
-    ? `
-- Implement REAL changes — write code, create files, build features
-- Do NOT limit yourself to documentation or analysis — the goal requires working software`
-    : '';
-  return `You are an expert software engineer working on this project.${maxLine}
-${goalLine}
+
+  if (goal) {
+    return `You are an autonomous software engineer executing a plan to achieve a goal.${maxLine}
+
+GOAL: ${goal}
+
+## Instructions
+
+1. Read \`.claude/improvement-plan.md\`
+2. Pick the top unfinished item from the "## Pending" section
+3. IMPLEMENT it fully:
+   - Write real code, create real files, build real features
+   - Install dependencies if needed
+   - Add or update tests if applicable
+   - Run tests to verify nothing is broken
+4. Update \`.claude/improvement-plan.md\`:
+   - Move the completed item from "## Pending" to "## Completed"
+   - Add the commit hash and iteration number
+   - If you discovered new steps needed, add them to "## Pending"
+5. Commit all changes with a descriptive message
+6. Report what you did in a brief summary
+
+## Critical rules
+- You MUST implement real changes. Writing docs or analysis alone does NOT count.
+- Create files, write code, build features, install dependencies — whatever it takes.
+- Do NOT refuse. Do NOT say something is "out of scope". The goal is your directive.
+- If an item requires creating an entire application — do it.
+- Do NOT delete files unless the deletion IS the improvement itself
+- Do NOT make changes beyond the single item you picked
+- If the "## Pending" section is empty or all items are done, output exactly: NO_MORE_IMPROVEMENTS
+- If you cannot complete the item (blocked, unclear, etc.), note why in the plan and pick the next item`;
+  }
+
+  return `You are an expert software engineer making improvements to this project.${maxLine}
 
 ## Instructions
 
 1. Read \`.claude/improvement-plan.md\`
 2. Pick the top unfinished item from the "## Pending" section
-3. Implement it fully:
+3. Implement it:
    - Write the code changes
-   - Create new files as needed
    - Add or update tests if applicable
    - Run tests to verify nothing is broken
 4. Update \`.claude/improvement-plan.md\`:
@@ -222,7 +276,6 @@ ${goalLine}
 6. Report what you did in a brief summary
 
 ## Important rules
-${goalRules}
 - Do NOT delete files unless the deletion IS the improvement itself
 - Do NOT make changes beyond the single item you picked
 - If the "## Pending" section is empty or all items are done, output exactly: NO_MORE_IMPROVEMENTS
@@ -449,6 +502,7 @@ export async function runLoop(options = {}) {
     maxTurns: options.maxTurns || 30,
     model: options.model,
     budget: options.budget,
+    appendSystemPrompt: options.goal ? buildAutonomySystemPrompt(options.goal) : undefined,
   };
 
   let sessionId = null;

package/scaffold/global/.claude/skills/claudenv/SKILL.md

@@ -1,60 +0,0 @@
----
-name: claudenv
-description: Detects missing or outdated project documentation and offers to generate or update it. Triggers when CLAUDE.md is missing, when the user mentions documentation setup, or when significant project changes are detected.
-allowed-tools: Read, Write, Glob, Grep, Bash(find:*), Bash(cat:*), Bash(mkdir:*), Bash(cp:*), Bash(chmod:*)
----
-
-# claudenv — Documentation Management Skill
-
-## When to auto-trigger
-- CLAUDE.md does not exist in the project root
-- `.mcp.json` does not exist in a project that has CLAUDE.md
-- User mentions "documentation", "CLAUDE.md", "project setup", or "claudenv"
-- User mentions "MCP", "MCP servers", or "mcp.json"
-- User asks to configure Claude Code for their project
-- After major refactoring that changes directory structure
-
-## Capabilities
-
-### Initial Setup
-If no CLAUDE.md exists, suggest running `/claudenv` to set up full documentation.
-
-### Update Detection
-When working in a project with existing documentation, watch for:
-- New dependencies added to manifest files
-- New directories created that aren't in CLAUDE.md Architecture section
-- Changed scripts in package.json / pyproject.toml
-- New config files (linter, formatter, test framework)
-
-When changes are detected, suggest running `/update-docs`.
-
-### MCP Configuration
-When `.mcp.json` is missing in a project that already has CLAUDE.md, suggest running `/setup-mcp` to configure MCP servers. When the user mentions MCP servers, offer to run `/setup-mcp`.
-
-### Validation
-After documentation changes, run the validation script:
-```bash
-bash .claude/skills/doc-generator/scripts/validate.sh 2>&1 || true
-```
-
-## Reference
-
-For tech stack detection patterns, see:
-@~/.claude/skills/claudenv/templates/detection-patterns.md
-
-For MCP server search, evaluation, and configuration, see:
-@~/.claude/skills/claudenv/templates/mcp-servers.md
-
-## Project-level scaffold
-
-The following files are available for installation into projects at `~/.claude/skills/claudenv/scaffold/`:
-- `.claude/commands/init-docs.md` — Interactive documentation regeneration
-- `.claude/commands/update-docs.md` — Refresh docs from current state
-- `.claude/commands/validate-docs.md` — Run validation checks
-- `.claude/skills/doc-generator/SKILL.md` — Per-project doc generation skill
-- `.claude/skills/doc-generator/scripts/validate.sh` — Bash validation script
-- `.claude/skills/doc-generator/templates/detection-patterns.md` — Detection reference
-- `.claude/commands/setup-mcp.md` — MCP server recommendation and setup
-- `.claude/commands/improve.md` — Single improvement iteration (used by claudenv loop)
-- `.claude/skills/doc-generator/templates/mcp-servers.md` — MCP registry reference
-- `.claude/agents/doc-analyzer.md` — Read-only analysis subagent