kspec 1.0.13 → 1.0.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kspec",
-  "version": "1.0.13",
+  "version": "1.0.15",
   "description": "Spec-driven development workflow for Kiro CLI",
   "main": "src/index.js",
   "bin": {

package/src/index.js

@@ -106,6 +106,9 @@ async function confirm(question) {
 }
 
 function chat(message, agent) {
+  // Refresh context before each chat to ensure LLM has latest state
+  refreshContext();
+
   const cli = requireCli();
   const args = agent ? ['chat', '--agent', agent, message] : ['chat', message];
   const child = spawn(cli, args, { stdio: 'inherit' });
@@ -175,6 +178,101 @@ function getTaskStats(folder) {
   return { total, done, remaining: total - done };
 }
 
+function getCurrentTask(folder) {
+  const tasksFile = path.join(folder, 'tasks.md');
+  if (!fs.existsSync(tasksFile)) return null;
+
+  const content = fs.readFileSync(tasksFile, 'utf8');
+  const lines = content.split('\n');
+  for (const line of lines) {
+    if (/^-\s*\[ \]/.test(line)) {
+      return line.replace(/^-\s*\[ \]\s*/, '').trim();
+    }
+  }
+  return null;
+}
+
+function refreshContext() {
+  const contextFile = path.join(KSPEC_DIR, 'CONTEXT.md');
+  const current = getCurrentSpec();
+
+  if (!current) {
+    // No current spec - create minimal context
+    const content = `# kspec Context
+
+No active spec. Run: \`kspec spec "Feature Name"\`
+`;
+    ensureDir(KSPEC_DIR);
+    fs.writeFileSync(contextFile, content);
+    return content;
+  }
+
+  const specName = path.basename(current);
+  const stats = getTaskStats(current);
+  const currentTask = getCurrentTask(current);
+
+  // Read spec-lite if exists
+  const specLiteFile = path.join(current, 'spec-lite.md');
+  let specLite = '';
+  if (fs.existsSync(specLiteFile)) {
+    specLite = fs.readFileSync(specLiteFile, 'utf8');
+  }
+
+  // Read memory if exists
+  const memoryFile = path.join(current, 'memory.md');
+  let memory = '';
+  if (fs.existsSync(memoryFile)) {
+    memory = fs.readFileSync(memoryFile, 'utf8');
+  }
+
+  // Build context
+  let content = `# kspec Context
+> Auto-generated. Always read this first after context compression.
+
+## Current Spec
+**${specName}**
+Path: \`${current}\`
+
+`;
+
+  if (stats) {
+    content += `## Progress
+- Tasks: ${stats.done}/${stats.total} completed
+- Remaining: ${stats.remaining}
+`;
+    if (currentTask) {
+      content += `- **Current Task**: ${currentTask}
+`;
+    }
+    content += '\n';
+  }
+
+  if (specLite) {
+    content += `## Requirements Summary
+${specLite}
+
+`;
+  }
+
+  if (memory) {
+    content += `## Decisions & Learnings
+${memory}
+
+`;
+  }
+
+  content += `## Quick Commands
+- \`kspec build\` - Continue building tasks
+- \`kspec verify\` - Verify implementation
+- \`kspec status\` - Show current status
+- \`kspec context\` - Refresh this file
+`;
+
+  ensureDir(KSPEC_DIR);
+  fs.writeFileSync(contextFile, content);
+  return content;
+}
+
 // Templates
 const steeringTemplates = {
   'product.md': `# Product Overview
@@ -221,17 +319,22 @@ const agentTemplates = {
     tools: ['read', 'write'],
     allowedTools: ['read', 'write'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec analyser. Your job:
+    prompt: `You are the kspec analyser.
+
+FIRST: Read .kspec/CONTEXT.md for current state and spec summary.
+
+Your job:
 1. Analyse the codebase structure, tech stack, patterns
 2. Review .kiro/steering/ docs
 3. Suggest updates to steering based on actual codebase
 4. Identify risks, tech debt, improvement areas
 
 Output a clear analysis report. Propose specific steering doc updates.`,
-    keyboardShortcut: 'ctrl+a',
+    keyboardShortcut: 'ctrl+shift+a',
     welcomeMessage: 'Analysing codebase...'
   },
 
@@ -242,25 +345,31 @@ Output a clear analysis report. Propose specific steering doc updates.`,
     tools: ['read', 'write'],
     allowedTools: ['read', 'write'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec specification writer. Your job:
+    prompt: `You are the kspec specification writer.
+
+WORKFLOW (do this autonomously):
 1. Read .kiro/steering/ for project context
-2. Create a comprehensive spec.md with:
+2. Create spec folder: .kspec/specs/YYYY-MM-DD-{feature-slug}/
+   - Use today's date and a short slug (2-4 words from feature name)
+3. Create spec.md in that folder with:
    - Problem/Context
    - Requirements (functional + non-functional)
    - Constraints
    - High-level design
    - Acceptance criteria
-3. IMMEDIATELY after spec.md, create spec-lite.md:
-   - Concise version (under 500 words)
+4. Create spec-lite.md (CRITICAL - under 500 words):
+   - Concise version for context retention after compression
    - Key requirements only
-   - Used for context after compression
+5. Update .kspec/.current with the spec folder path
+6. Update .kspec/CONTEXT.md with current state
 
-Always create both files. spec-lite.md is critical for context retention.`,
-    keyboardShortcut: 'ctrl+s',
-    welcomeMessage: 'Ready to create specification.'
+After completion, suggest: "Switch to kspec-tasks agent to generate implementation tasks"`,
+    keyboardShortcut: 'ctrl+shift+s',
+    welcomeMessage: 'Ready to create specification. Describe your feature.'
   },
 
   'kspec-tasks.json': {
@@ -270,21 +379,29 @@ Always create both files. spec-lite.md is critical for context retention.`,
     tools: ['read', 'write'],
     allowedTools: ['read', 'write'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec task generator. Your job:
-1. Read spec.md and spec-lite.md from the spec folder
-2. Generate tasks.md with:
+    prompt: `You are the kspec task generator.
+
+WORKFLOW:
+1. Read .kspec/CONTEXT.md for current spec location
+2. Read .kspec/.current to get spec folder path
+3. Read spec.md and spec-lite.md from that folder
+4. Generate tasks.md in the spec folder with:
    - Checkbox format: "- [ ] Task description"
    - TDD approach: test first, then implement
    - Logical ordering (models → services → API → UI)
    - Dependencies noted
    - File paths where changes occur
+5. Update .kspec/CONTEXT.md with task count
+
+Tasks must be atomic and independently verifiable.
 
-Tasks must be atomic and independently verifiable.`,
-    keyboardShortcut: 'ctrl+t',
-    welcomeMessage: 'Generating tasks from spec...'
+After completion, suggest: "Switch to kspec-build agent to start implementing tasks"`,
+    keyboardShortcut: 'ctrl+shift+t',
+    welcomeMessage: 'Reading current spec and generating tasks...'
   },
 
   'kspec-build.json': {
@@ -294,24 +411,34 @@ Tasks must be atomic and independently verifiable.`,
     tools: ['read', 'write', 'shell'],
     allowedTools: ['read', 'write', 'shell'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec builder. Your job:
-1. Read tasks.md, find first uncompleted task (- [ ])
-2. For each task:
+    prompt: `You are the kspec builder.
+
+WORKFLOW:
+1. Read .kspec/CONTEXT.md for current spec and task progress
+2. Read .kspec/.current to get spec folder path
+3. Read tasks.md from spec folder, find first uncompleted task (- [ ])
+4. For each task:
    a) Write test first (TDD)
    b) Implement minimal code to pass
    c) Run tests
    d) Mark task complete: change "- [ ]" to "- [x]"
    e) Update tasks.md file
-3. Commit after each task
-
-CRITICAL: Always update tasks.md after completing each task.
-NEVER delete .kiro or .kspec folders.
-Use non-interactive flags for commands (--yes, -y).`,
-    keyboardShortcut: 'ctrl+b',
-    welcomeMessage: 'Building from tasks...'
+   f) Update .kspec/CONTEXT.md with new progress
+5. Commit after each task with descriptive message
+
+CRITICAL:
+- Always update tasks.md after completing each task
+- Update .kspec/CONTEXT.md with current task and progress
+- NEVER delete .kiro or .kspec folders
+- Use non-interactive flags for commands (--yes, -y)
+
+When all tasks complete, suggest: "Switch to kspec-verify agent to verify implementation"`,
+    keyboardShortcut: 'ctrl+shift+b',
+    welcomeMessage: 'Reading current task and building...'
   },
 
   'kspec-verify.json': {
@@ -321,10 +448,15 @@ Use non-interactive flags for commands (--yes, -y).`,
     tools: ['read', 'shell'],
     allowedTools: ['read', 'shell'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec verifier. Based on what you're asked to verify:
+    prompt: `You are the kspec verifier.
+
+FIRST: Read .kspec/CONTEXT.md for current spec and progress.
+
+Based on what you're asked to verify:
 
 VERIFY-SPEC:
 - Check spec covers all requirements
@@ -345,7 +477,7 @@ VERIFY-IMPLEMENTATION:
 - List any gaps between spec and implementation
 
 Output a clear verification report with pass/fail status.`,
-    keyboardShortcut: 'ctrl+v',
+    keyboardShortcut: 'ctrl+shift+v',
     welcomeMessage: 'What should I verify?'
   },
 
@@ -356,10 +488,15 @@ Output a clear verification report with pass/fail status.`,
     tools: ['read', 'shell'],
     allowedTools: ['read', 'shell'],
     resources: [
+      'file://.kspec/CONTEXT.md',
       'file://.kiro/steering/**/*.md',
       'file://.kspec/**/*.md'
     ],
-    prompt: `You are the kspec code reviewer. Your job:
+    prompt: `You are the kspec code reviewer.
+
+FIRST: Read .kspec/CONTEXT.md for current spec context.
+
+Your job:
 1. Review code changes (git diff or specified files)
 2. Check compliance with .kiro/steering/
 3. Evaluate:
@@ -370,7 +507,7 @@ Output a clear verification report with pass/fail status.`,
 4. Provide actionable feedback
 
 Output: APPROVE / REQUEST_CHANGES with specific issues.`,
-    keyboardShortcut: 'ctrl+r',
+    keyboardShortcut: 'ctrl+shift+r',
     welcomeMessage: 'Ready to review. What should I look at?'
   }
 };
@@ -632,13 +769,13 @@ Output: APPROVE or REQUEST_CHANGES with specifics.`, 'kspec-review');
 
   status() {
     const current = getCurrentSpec();
-    
+
     console.log('\nkspec Status\n');
     console.log(`CLI: ${detectCli() || '(not installed)'}`);
     console.log(`Initialized: ${config.initialized ? 'yes' : 'no'}`);
     console.log(`Date format: ${config.dateFormat || 'YYYY-MM-DD'}`);
     console.log(`Auto-execute: ${config.autoExecute || 'ask'}`);
-    
+
     if (current) {
       console.log(`\nCurrent spec: ${path.basename(current)}`);
       const stats = getTaskStats(current);
@@ -658,18 +795,24 @@ Output: APPROVE or REQUEST_CHANGES with specifics.`, 'kspec-review');
     console.log('');
   },
 
+  context() {
+    const content = refreshContext();
+    console.log(content);
+    console.log(`Context saved to: .kspec/CONTEXT.md\n`);
+  },
+
   agents() {
     console.log(`
 kspec Agents
 
 Agent           Shortcut  Purpose
 ─────────────────────────────────────────────
-kspec-analyse   Ctrl+A    Analyse codebase, update steering
-kspec-spec      Ctrl+S    Create specifications
-kspec-tasks     Ctrl+T    Generate tasks from spec
-kspec-build     Ctrl+B    Execute tasks with TDD
-kspec-verify    Ctrl+V    Verify spec/tasks/implementation
-kspec-review    Ctrl+R    Code review
+kspec-analyse   Ctrl+Shift+A    Analyse codebase, update steering
+kspec-spec      Ctrl+Shift+S    Create specifications
+kspec-tasks     Ctrl+Shift+T    Generate tasks from spec
+kspec-build     Ctrl+Shift+B    Execute tasks with TDD
+kspec-verify    Ctrl+Shift+V    Verify spec/tasks/implementation
+kspec-review    Ctrl+Shift+R    Code review
 
 Switch: /agent swap or use keyboard shortcuts
 `);
@@ -679,7 +822,7 @@ Switch: /agent swap or use keyboard shortcuts
     console.log(`
 kspec - Spec-driven development for Kiro CLI
 
-Workflow:
+CLI Workflow (outside kiro-cli):
   kspec init              Interactive setup
   kspec analyse           Analyse codebase, update steering
   kspec spec "Feature"    Create specification
@@ -690,22 +833,26 @@ Workflow:
   kspec verify            Verify implementation
   kspec done              Complete spec, harvest memory
 
+Inside kiro-cli (recommended):
+  /agent swap kspec-spec    → Describe feature → creates spec
+  /agent swap kspec-tasks   → Generates tasks from spec
+  /agent swap kspec-build   → Builds tasks with TDD
+  /agent swap kspec-verify  → Verifies implementation
+
+  Agents read .kspec/CONTEXT.md automatically for state.
+
 Other:
+  kspec context           Refresh/view context file
   kspec review [target]   Code review
   kspec list              List all specs
   kspec status            Current status
   kspec agents            List agents
   kspec help              Show this help
-  kspec --help, -h        Show this help
-  kspec --version, -v     Show version
 
 Examples:
-  kspec init
-  kspec spec "User Authentication"
-  kspec tasks
-  kspec build
-  kspec verify
-  kspec done
+  kspec init                        # First time setup
+  kspec spec "User Auth"            # CLI mode
+  kiro-cli --agent kspec-spec       # Direct agent mode
 `);
   }
 };
@@ -732,4 +879,4 @@ async function run(args) {
   }
 }
 
-module.exports = { run, commands, loadConfig, detectCli, requireCli, agentTemplates, getTaskStats };
+module.exports = { run, commands, loadConfig, detectCli, requireCli, agentTemplates, getTaskStats, refreshContext, getCurrentTask };