deepflow 0.1.20 → 0.1.22

package/hooks/df-check-update.js

@@ -12,7 +12,6 @@ const os = require('os');
 const PACKAGE_NAME = 'deepflow';
 const CACHE_DIR = path.join(os.homedir(), '.claude', 'cache');
 const CACHE_FILE = path.join(CACHE_DIR, 'df-update-check.json');
-const CHECK_INTERVAL = 24 * 60 * 60 * 1000; // 24 hours
 
 // If called directly, spawn background process and exit
 if (process.argv[2] !== '--background') {
@@ -32,15 +31,6 @@ async function checkForUpdate() {
       fs.mkdirSync(CACHE_DIR, { recursive: true });
     }
 
-    // Check if we've checked recently
-    if (fs.existsSync(CACHE_FILE)) {
-      const cache = JSON.parse(fs.readFileSync(CACHE_FILE, 'utf8'));
-      const age = Date.now() - (cache.timestamp || 0);
-      if (age < CHECK_INTERVAL) {
-        process.exit(0);
-      }
-    }
-
     // Get current version
     const currentVersion = getCurrentVersion();
     if (!currentVersion) {
@@ -92,8 +82,7 @@ function getLatestVersion() {
     const timeout = setTimeout(() => resolve(null), 10000);
 
     const child = spawn('npm', ['view', PACKAGE_NAME, 'version'], {
-      stdio: ['ignore', 'pipe', 'ignore'],
-      shell: true
+      stdio: ['ignore', 'pipe', 'ignore']
     });
 
     let output = '';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepflow",
-  "version": "0.1.20",
+  "version": "0.1.22",
   "description": "Stay in flow state - lightweight spec-driven task orchestration for Claude Code",
   "keywords": [
     "claude",

package/src/commands/df/plan.md

@@ -1,7 +1,7 @@
 # /df:plan — Generate Task Plan from Specs
 
 ## Purpose
-Compare specs against codebase AND past experiments, identify gaps, generate prioritized task list informed by historical learnings.
+Compare specs against codebase and past experiments. Generate prioritized tasks.
 
 ## Usage
 ```
@@ -44,32 +44,19 @@ If no new specs: report counts, suggest `/df:execute`.
 
 ### 2. CHECK PAST EXPERIMENTS
 
-Before proposing approaches, learn from history:
+Extract domains from spec (perf, auth, api, etc.), then:
 
 ```
-1. Extract domains from spec keywords (performance, auth, caching, api, etc.)
-2. Glob `.deepflow/experiments/{domain}--*`
-3. Read matching files (filenames are the index, minimal token cost)
-4. Note failed approaches to avoid
-5. Note successful patterns to reuse
+Glob .deepflow/experiments/{domain}--*
 ```
 
-**If experiments found:**
-- Failed: Exclude approach from plan, note why
-- Success: Reference as pattern to follow
-
-**File naming convention:**
-```
-.deepflow/experiments/
-  {domain}--{approach}--{result}.md
-
-Examples:
-  perf--redis-caching--failed.md
-  perf--connection-pooling--success.md
-  auth--jwt-refresh--success.md
-```
+| Result | Action |
+|--------|--------|
+| `--failed.md` | Exclude approach, note why |
+| `--success.md` | Reference as pattern |
+| No matches | Continue (expected for new projects) |
 
-**No experiments?** Continue normally—this is expected for new projects.
+**Naming:** `{domain}--{approach}--{result}.md`
 
 ### 3. DETECT PROJECT CONTEXT
 
@@ -117,30 +104,17 @@ Include patterns in task descriptions for agents to follow.
 
 ### 6. VALIDATE HYPOTHESES
 
-Before finalizing the plan, identify and test risky assumptions:
-
-**When to validate:**
-- Unfamiliar APIs or libraries
-- Architectural decisions with multiple approaches
-- Integration with external systems
-- Performance-critical paths
-
-**How to validate:**
-1. Create minimal prototype (scratchpad, not committed)
-2. Test the specific assumption
-3. If fails: Write to `.deepflow/experiments/{domain}--{approach}--failed.md`
-4. Adjust approach based on findings
-5. Document learnings in task description
-
-**Examples:**
-- "Does SessionStart hook run once per session?" → Test with simple log
-- "Can we use streaming for large files?" → Prototype with sample data
-- "Will this regex handle edge cases?" → Test against real samples
-
-**Skip validation when:**
-- Using well-known patterns
-- Simple CRUD operations
-- Clear documentation exists
+Test risky assumptions before finalizing plan.
+
+**Validate when:** Unfamiliar APIs, multiple approaches possible, external integrations, performance-critical
+
+**Process:**
+1. Prototype in scratchpad (not committed)
+2. Test assumption
+3. If fails → Write `.deepflow/experiments/{domain}--{approach}--failed.md`
+4. Adjust approach, document in task
+
+**Skip:** Well-known patterns, simple CRUD, clear docs exist
 
 ### 7. OUTPUT PLAN.md
 

package/src/commands/df/verify.md

@@ -48,30 +48,24 @@ If issues: suggest creating fix spec or reopening (`mv done-* doing-*`).
 
 ### 4. CAPTURE LEARNINGS
 
-After successful verification, document significant learnings:
+On success, write significant learnings to `.deepflow/experiments/{domain}--{approach}--success.md`
 
-**When to write experiment:**
-- Non-trivial implementation approach was used
-- Alternative approaches were considered/rejected during planning
-- Performance optimizations were made
-- Integration patterns were discovered
-
-**Write to:** `.deepflow/experiments/{domain}--{approach}--success.md`
+**Write when:**
+- Non-trivial approach used
+- Alternatives rejected during planning
+- Performance optimization made
+- Integration pattern discovered
 
 **Format:**
 ```markdown
 # {Approach} [SUCCESS]
-Objective: {What was the goal}
-Context: {Spec reference, why this was needed}
-Approach: {What was implemented}
-Why it worked: {Key insight}
-Files: {Main files involved}
+Objective: ...
+Approach: ...
+Why it worked: ...
+Files: ...
 ```
 
-**Skip when:**
-- Simple CRUD, no learnings
-- Standard patterns, well-documented
-- User declines ("No significant learnings")
+**Skip:** Simple CRUD, standard patterns, user declines
 
 ## Verification Levels