lean-spec 0.2.6 → 0.2.7-dev.20251126090633

package/dist/cli.js

@@ -1,4 +1,4 @@
-import { analyzeCommand, archiveCommand, backfillCommand, boardCommand, checkCommand, compactCommand, createCommand, depsCommand, examplesCommand, filesCommand, ganttCommand, initCommand, linkCommand, listCommand, mcpCommand, migrateCommand, openCommand, searchCommand, splitCommand, statsCommand, templatesCommand, timelineCommand, tokensCommand, uiCommand, unlinkCommand, updateCommand, validateCommand, viewCommand } from './chunk-RTEGSMVL.js';
+import { agentCommand, analyzeCommand, archiveCommand, backfillCommand, boardCommand, checkCommand, compactCommand, createCommand, depsCommand, examplesCommand, filesCommand, ganttCommand, initCommand, linkCommand, listCommand, mcpCommand, migrateCommand, openCommand, searchCommand, splitCommand, statsCommand, templatesCommand, timelineCommand, tokensCommand, uiCommand, unlinkCommand, updateCommand, validateCommand, viewCommand } from './chunk-GSBLCPXH.js';
 import './chunk-LVD7ZAVZ.js';
 import { Command } from 'commander';
 import { readFileSync } from 'fs';
@@ -7,6 +7,7 @@ import { dirname, join } from 'path';
 
 // src/commands/registry.ts
 function registerCommands(program2) {
+  program2.addCommand(agentCommand());
   program2.addCommand(analyzeCommand());
   program2.addCommand(archiveCommand());
   program2.addCommand(backfillCommand());
@@ -87,6 +88,7 @@ Command Groups:
     templates                     Manage spec templates
     
   Integration:
+    agent                         Dispatch specs to AI coding agents
     mcp                           Start MCP server for AI assistants
     ui                            Start local web UI for spec management
 
@@ -112,6 +114,9 @@ Examples:
   $ lean-spec tokens 059
   $ lean-spec analyze 045 --json
   $ lean-spec split 045 --output README.md:1-150 --output DESIGN.md:151-end
+  $ lean-spec agent list
+  $ lean-spec agent run 045 --agent claude
+  $ lean-spec agent run 045 047 048 --parallel
   $ lean-spec ui
   $ lean-spec ui --port 3001 --no-open
   $ lean-spec ui --specs ./docs/specs --dry-run

package/dist/cli.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../src/commands/registry.ts","../src/cli.ts"],"names":["program"],"mappings":";;;;;;;;AAmCO,SAAS,iBAAiBA,QAAAA,EAAwB;AAEvD,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,UAAA,EAAY,CAAA;AAC/B,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,gBAAA,EAAkB,CAAA;AACrC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,SAAA,EAAW,CAAA;AAC9B,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAClC;;;AC1DA,IAAM,UAAA,GAAa,aAAA,CAAc,MAAA,CAAA,IAAA,CAAY,GAAG,CAAA;AAChD,IAAM,SAAA,GAAY,QAAQ,UAAU,CAAA;AACpC,IAAM,cAAc,IAAA,CAAK,KAAA;AAAA,EACvB,YAAA,CAAa,IAAA,CAAK,SAAA,EAAW,iBAAiB,GAAG,OAAO;AAC1D,CAAA;AAEA,IAAM,OAAA,GAAU,IAAI,OAAA,EAAQ;AAE5B,OAAA,CACG,IAAA,CAAK,WAAW,CAAA,CAChB,WAAA,CAAY,2BAA2B,CAAA,CACvC,OAAA,CAAQ,YAAY,OAAO,CAAA;AAG9B,OAAA,CAAQ,YAAY,OAAA,EAAS;AAAA;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,CAsE5B,CAAA;AAGD,gBAAA,CAAiB,OAAO,CAAA;AAGxB,OAAA,CAAQ,KAAA,EAAM","file":"cli.js","sourcesContent":["import { Command } from 'commander';\nimport {\n  analyzeCommand,\n  archiveCommand,\n  backfillCommand,\n  boardCommand,\n  checkCommand,\n  compactCommand,\n  createCommand,\n  depsCommand,\n  examplesCommand,\n  filesCommand,\n  ganttCommand,\n  initCommand,\n  linkCommand,\n  listCommand,\n  mcpCommand,\n  migrateCommand,\n  openCommand,\n  searchCommand,\n  splitCommand,\n  statsCommand,\n  templatesCommand,\n  timelineCommand,\n  tokensCommand,\n  uiCommand,\n  unlinkCommand,\n  updateCommand,\n  validateCommand,\n  viewCommand,\n} from './index.js';\n\n/**\n * Register all commands in alphabetical order\n */\nexport function registerCommands(program: Command): void {\n  // Alphabetically sorted command registration\n  program.addCommand(analyzeCommand());\n  program.addCommand(archiveCommand());\n  program.addCommand(backfillCommand());\n  program.addCommand(boardCommand());\n  program.addCommand(checkCommand());\n  program.addCommand(compactCommand());\n  program.addCommand(createCommand());\n  program.addCommand(depsCommand());\n  program.addCommand(examplesCommand());\n  program.addCommand(filesCommand());\n  program.addCommand(ganttCommand());\n  program.addCommand(initCommand());\n  program.addCommand(linkCommand());\n  program.addCommand(listCommand());\n  program.addCommand(mcpCommand());\n  program.addCommand(migrateCommand());\n  program.addCommand(openCommand());\n  program.addCommand(searchCommand());\n  program.addCommand(splitCommand());\n  program.addCommand(statsCommand());\n  program.addCommand(templatesCommand());\n  program.addCommand(timelineCommand());\n  program.addCommand(tokensCommand());\n  program.addCommand(uiCommand());\n  program.addCommand(unlinkCommand());\n  program.addCommand(updateCommand());\n  program.addCommand(validateCommand());\n  program.addCommand(viewCommand());\n}\n","import { Command } from 'commander';\nimport { readFileSync } from 'fs';\nimport { fileURLToPath } from 'url';\nimport { dirname, join } from 'path';\nimport { registerCommands } from './commands/registry.js';\n\n// Get version from package.json\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = dirname(__filename);\nconst packageJson = JSON.parse(\n  readFileSync(join(__dirname, '../package.json'), 'utf-8')\n);\n\nconst program = new Command();\n\nprogram\n  .name('lean-spec')\n  .description('Manage LeanSpec documents')\n  .version(packageJson.version);\n\n// Add custom help text with grouped commands\nprogram.addHelpText('after', `\nCommand Groups:\n\n  Core Workflow:\n    archive <spec>                Move spec to archived/\n    backfill [specs...]           Backfill timestamps from git history\n    create <name>                 Create new spec\n    examples                      List example projects for tutorials\n    init                          Initialize LeanSpec in current directory\n    link <spec>                   Add relationships between specs\n    migrate <input-path>          Migrate specs from other SDD tools\n    unlink <spec>                 Remove relationships between specs\n    update <spec>                 Update spec metadata\n    \n  Discovery & Search:\n    files <spec>                  List files in a spec\n    list                          List all specs\n    open <spec>                   Open spec in editor\n    search <query>                Full-text search with metadata filters\n    view <spec>                   View spec content\n    \n  Project Analytics:\n    board                         Show Kanban-style board view\n    deps <spec>                   Show dependency graph for a spec\n    gantt                         Show timeline with dependencies\n    stats                         Show aggregate statistics\n    timeline                      Show creation/completion over time\n    \n  Quality & Optimization:\n    analyze <spec>                Analyze spec complexity and structure\n    check                         Check for sequence conflicts\n    tokens [spec]                 Count tokens for LLM context management\n    validate [specs...]           Validate specs for quality issues\n    \n  Advanced Editing:\n    compact <spec>                Remove specified line ranges from spec\n    split <spec>                  Split spec into multiple files\n    \n  Configuration:\n    templates                     Manage spec templates\n    \n  Integration:\n    mcp                           Start MCP server for AI assistants\n    ui                            Start local web UI for spec management\n\nExamples:\n  $ lean-spec init\n  $ lean-spec init -y\n  $ lean-spec init --example dark-theme\n  $ lean-spec init --example dashboard-widgets --name my-demo\n  $ lean-spec examples\n  $ lean-spec create my-feature --priority high\n  $ lean-spec list --status in-progress\n  $ lean-spec view 042\n  $ lean-spec link 085 --depends-on 042,035\n  $ lean-spec link 085 --related 082\n  $ lean-spec unlink 085 --depends-on 042\n  $ lean-spec deps 085\n  $ lean-spec backfill --dry-run\n  $ lean-spec migrate ./docs/adr\n  $ lean-spec migrate ./docs/rfcs --with copilot\n  $ lean-spec board --tag backend\n  $ lean-spec search \"authentication\"\n  $ lean-spec validate\n  $ lean-spec tokens 059\n  $ lean-spec analyze 045 --json\n  $ lean-spec split 045 --output README.md:1-150 --output DESIGN.md:151-end\n  $ lean-spec ui\n  $ lean-spec ui --port 3001 --no-open\n  $ lean-spec ui --specs ./docs/specs --dry-run\n`);\n\n// Register all commands (alphabetically ordered)\nregisterCommands(program);\n\n// Parse and execute\nprogram.parse();\n"]}
+{"version":3,"sources":["../src/commands/registry.ts","../src/cli.ts"],"names":["program"],"mappings":";;;;;;;;AAoCO,SAAS,iBAAiBA,QAAAA,EAAwB;AAEvD,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,UAAA,EAAY,CAAA;AAC/B,EAAAA,QAAAA,CAAQ,UAAA,CAAW,cAAA,EAAgB,CAAA;AACnC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAChC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,YAAA,EAAc,CAAA;AACjC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,gBAAA,EAAkB,CAAA;AACrC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,SAAA,EAAW,CAAA;AAC9B,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,aAAA,EAAe,CAAA;AAClC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,eAAA,EAAiB,CAAA;AACpC,EAAAA,QAAAA,CAAQ,UAAA,CAAW,WAAA,EAAa,CAAA;AAClC;;;AC5DA,IAAM,UAAA,GAAa,aAAA,CAAc,MAAA,CAAA,IAAA,CAAY,GAAG,CAAA;AAChD,IAAM,SAAA,GAAY,QAAQ,UAAU,CAAA;AACpC,IAAM,cAAc,IAAA,CAAK,KAAA;AAAA,EACvB,YAAA,CAAa,IAAA,CAAK,SAAA,EAAW,iBAAiB,GAAG,OAAO;AAC1D,CAAA;AAEA,IAAM,OAAA,GAAU,IAAI,OAAA,EAAQ;AAE5B,OAAA,CACG,IAAA,CAAK,WAAW,CAAA,CAChB,WAAA,CAAY,2BAA2B,CAAA,CACvC,OAAA,CAAQ,YAAY,OAAO,CAAA;AAG9B,OAAA,CAAQ,YAAY,OAAA,EAAS;AAAA;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,CA0E5B,CAAA;AAGD,gBAAA,CAAiB,OAAO,CAAA;AAGxB,OAAA,CAAQ,KAAA,EAAM","file":"cli.js","sourcesContent":["import { Command } from 'commander';\nimport {\n  agentCommand,\n  analyzeCommand,\n  archiveCommand,\n  backfillCommand,\n  boardCommand,\n  checkCommand,\n  compactCommand,\n  createCommand,\n  depsCommand,\n  examplesCommand,\n  filesCommand,\n  ganttCommand,\n  initCommand,\n  linkCommand,\n  listCommand,\n  mcpCommand,\n  migrateCommand,\n  openCommand,\n  searchCommand,\n  splitCommand,\n  statsCommand,\n  templatesCommand,\n  timelineCommand,\n  tokensCommand,\n  uiCommand,\n  unlinkCommand,\n  updateCommand,\n  validateCommand,\n  viewCommand,\n} from './index.js';\n\n/**\n * Register all commands in alphabetical order\n */\nexport function registerCommands(program: Command): void {\n  // Alphabetically sorted command registration\n  program.addCommand(agentCommand());\n  program.addCommand(analyzeCommand());\n  program.addCommand(archiveCommand());\n  program.addCommand(backfillCommand());\n  program.addCommand(boardCommand());\n  program.addCommand(checkCommand());\n  program.addCommand(compactCommand());\n  program.addCommand(createCommand());\n  program.addCommand(depsCommand());\n  program.addCommand(examplesCommand());\n  program.addCommand(filesCommand());\n  program.addCommand(ganttCommand());\n  program.addCommand(initCommand());\n  program.addCommand(linkCommand());\n  program.addCommand(listCommand());\n  program.addCommand(mcpCommand());\n  program.addCommand(migrateCommand());\n  program.addCommand(openCommand());\n  program.addCommand(searchCommand());\n  program.addCommand(splitCommand());\n  program.addCommand(statsCommand());\n  program.addCommand(templatesCommand());\n  program.addCommand(timelineCommand());\n  program.addCommand(tokensCommand());\n  program.addCommand(uiCommand());\n  program.addCommand(unlinkCommand());\n  program.addCommand(updateCommand());\n  program.addCommand(validateCommand());\n  program.addCommand(viewCommand());\n}\n","import { Command } from 'commander';\nimport { readFileSync } from 'fs';\nimport { fileURLToPath } from 'url';\nimport { dirname, join } from 'path';\nimport { registerCommands } from './commands/registry.js';\n\n// Get version from package.json\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = dirname(__filename);\nconst packageJson = JSON.parse(\n  readFileSync(join(__dirname, '../package.json'), 'utf-8')\n);\n\nconst program = new Command();\n\nprogram\n  .name('lean-spec')\n  .description('Manage LeanSpec documents')\n  .version(packageJson.version);\n\n// Add custom help text with grouped commands\nprogram.addHelpText('after', `\nCommand Groups:\n\n  Core Workflow:\n    archive <spec>                Move spec to archived/\n    backfill [specs...]           Backfill timestamps from git history\n    create <name>                 Create new spec\n    examples                      List example projects for tutorials\n    init                          Initialize LeanSpec in current directory\n    link <spec>                   Add relationships between specs\n    migrate <input-path>          Migrate specs from other SDD tools\n    unlink <spec>                 Remove relationships between specs\n    update <spec>                 Update spec metadata\n    \n  Discovery & Search:\n    files <spec>                  List files in a spec\n    list                          List all specs\n    open <spec>                   Open spec in editor\n    search <query>                Full-text search with metadata filters\n    view <spec>                   View spec content\n    \n  Project Analytics:\n    board                         Show Kanban-style board view\n    deps <spec>                   Show dependency graph for a spec\n    gantt                         Show timeline with dependencies\n    stats                         Show aggregate statistics\n    timeline                      Show creation/completion over time\n    \n  Quality & Optimization:\n    analyze <spec>                Analyze spec complexity and structure\n    check                         Check for sequence conflicts\n    tokens [spec]                 Count tokens for LLM context management\n    validate [specs...]           Validate specs for quality issues\n    \n  Advanced Editing:\n    compact <spec>                Remove specified line ranges from spec\n    split <spec>                  Split spec into multiple files\n    \n  Configuration:\n    templates                     Manage spec templates\n    \n  Integration:\n    agent                         Dispatch specs to AI coding agents\n    mcp                           Start MCP server for AI assistants\n    ui                            Start local web UI for spec management\n\nExamples:\n  $ lean-spec init\n  $ lean-spec init -y\n  $ lean-spec init --example dark-theme\n  $ lean-spec init --example dashboard-widgets --name my-demo\n  $ lean-spec examples\n  $ lean-spec create my-feature --priority high\n  $ lean-spec list --status in-progress\n  $ lean-spec view 042\n  $ lean-spec link 085 --depends-on 042,035\n  $ lean-spec link 085 --related 082\n  $ lean-spec unlink 085 --depends-on 042\n  $ lean-spec deps 085\n  $ lean-spec backfill --dry-run\n  $ lean-spec migrate ./docs/adr\n  $ lean-spec migrate ./docs/rfcs --with copilot\n  $ lean-spec board --tag backend\n  $ lean-spec search \"authentication\"\n  $ lean-spec validate\n  $ lean-spec tokens 059\n  $ lean-spec analyze 045 --json\n  $ lean-spec split 045 --output README.md:1-150 --output DESIGN.md:151-end\n  $ lean-spec agent list\n  $ lean-spec agent run 045 --agent claude\n  $ lean-spec agent run 045 047 048 --parallel\n  $ lean-spec ui\n  $ lean-spec ui --port 3001 --no-open\n  $ lean-spec ui --specs ./docs/specs --dry-run\n`);\n\n// Register all commands (alphabetically ordered)\nregisterCommands(program);\n\n// Parse and execute\nprogram.parse();\n"]}

package/dist/mcp-server.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-export { createMcpServer } from './chunk-RTEGSMVL.js';
+export { createMcpServer } from './chunk-GSBLCPXH.js';
 import './chunk-LVD7ZAVZ.js';
 //# sourceMappingURL=mcp-server.js.map
 //# sourceMappingURL=mcp-server.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lean-spec",
-  "version": "0.2.6",
+  "version": "0.2.7-dev.20251126090633",
   "description": "Specification-driven development made simple",
   "type": "module",
   "bin": {
@@ -67,7 +67,7 @@
     "zod": "^3.25.76"
   },
   "devDependencies": {
-    "@leanspec/core": "^0.2.6",
+    "@leanspec/core": "workspace:*",
     "@types/js-yaml": "^4.0.9",
     "@types/marked-terminal": "^6.1.1",
     "@types/node": "^20.10.0",

package/templates/detailed/AGENTS.md

@@ -2,112 +2,157 @@
 
 ## Project: {project_name}
 
-Lightweight spec methodology for AI-powered development.
+<!-- ═══════════════════════════════════════════════════════════════════════════
+     👇 TODO: Fill in your project context below (then delete these comments)
+     ═══════════════════════════════════════════════════════════════════════════ -->
+
+### 📋 Project Context
+
+**What this project does:**
+_TODO: Describe your project in 1-2 sentences_
+
+**Tech stack:**
+_TODO: List main technologies (e.g., Node.js, React, PostgreSQL)_
+
+**Key objectives:**
+_TODO: What are you building toward? (e.g., Launch MVP by Q1)_
+
+<!-- ═══════════════════════════════════════════════════════════════════════════
+     👆 End of TODO section - Delete these comment markers when done
+     ═══════════════════════════════════════════════════════════════════════════ -->
+
+## 🚨 CRITICAL: Before ANY Task
+
+**STOP and check these first:**
+
+1. **Discover context** → Use `board` tool to see project state
+2. **Search for related work** → Use `search` tool before creating new specs
+3. **Never create files manually** → Always use `create` tool for new specs
+
+> **Why?** Skipping discovery creates duplicate work. Manual file creation breaks LeanSpec tooling.
+
+## 🔧 How to Manage Specs
+
+### Primary Method: MCP Tools (Recommended)
+
+If you have LeanSpec MCP tools available, **ALWAYS use them**:
+
+| Action | MCP Tool | Description |
+|--------|----------|-------------|
+| See project status | `board` | Kanban view + project health metrics |
+| List all specs | `list` | Filterable list with metadata |
+| Search specs | `search` | Semantic search across all content |
+| View a spec | `view` | Full content with formatting |
+| Create new spec | `create` | Auto-sequences, proper structure |
+| Update spec | `update` | Validates transitions, timestamps |
+| Check dependencies | `deps` | Visual dependency graph |
+
+**Why MCP over CLI?**
+- ✅ Direct tool integration (no shell execution needed)
+- ✅ Structured responses (better for AI reasoning)
+- ✅ Real-time validation (immediate feedback)
+- ✅ Context-aware (understands project state)
+
+### Fallback: CLI Commands
+
+If MCP tools are not available, use CLI commands:
+
+```bash
+lean-spec board              # Project overview
+lean-spec list               # See all specs
+lean-spec search "query"     # Find relevant specs
+lean-spec create <name>      # Create new spec
+lean-spec update <spec> --status <status>  # Update status
+lean-spec deps <spec>        # Show dependencies
+```
+
+**Tip:** Check if you have LeanSpec MCP tools available before using CLI.
+
+## ⚠️ SDD Workflow Checkpoints
+
+### Before Starting ANY Task
+
+1. 📋 **Run `board`** - What's the current project state?
+2. 🔍 **Run `search`** - Are there related specs already?
+3. 📝 **Check existing specs** - Is there one for this work?
+
+### During Implementation
+
+4. 📊 **Update status to `in-progress`** BEFORE coding
+5. 📝 **Document decisions** in the spec as you work
+6. 🔗 **Link related specs** if you discover connections
+
+### After Completing Work
+
+7. ✅ **Update status to `complete`** when done
+8. 📄 **Document what you learned** in the spec
+9. 🤔 **Create follow-up specs** if needed
+
+### 🚫 Common Mistakes to Avoid
+
+| ❌ Don't | ✅ Do Instead |
+|----------|---------------|
+| Create spec files manually | Use `create` tool |
+| Skip discovery before new work | Run `board` and `search` first |
+| Leave status as "planned" after starting | Update to `in-progress` immediately |
+| Finish work without updating spec | Document decisions, update status |
+| Edit frontmatter manually | Use `update` tool |
+| Forget about specs mid-conversation | Check spec status periodically |
 
 ## Core Rules
 
 1. **Read README.md first** - Understand project context
 2. **Check specs/** - Review existing specs before starting
-3. **Use `lean-spec --help`** - When unsure about commands, check the built-in help
+3. **Use MCP tools** - Prefer MCP over CLI when available
 4. **Follow LeanSpec principles** - Clarity over documentation
 5. **Keep it minimal** - If it doesn't add clarity, cut it
-6. **NEVER manually edit system-managed frontmatter** - Fields like `status`, `priority`, `tags`, `assignee`, `transitions`, `created_at`, `updated_at`, `completed_at`, `depends_on`, `related` are system-managed. Always use `lean-spec update`, `lean-spec link`, `lean-spec unlink`, or `lean-spec create` commands. Manual edits will cause metadata corruption and tracking issues.
-7. **Never use nested code blocks** - Markdown doesn't support code blocks within code blocks. If you need to show code examples in documentation, use indentation or describe the structure instead of nesting backticks.
+6. **NEVER manually edit frontmatter** - Use `update`, `link`, `unlink` tools
+7. **Track progress in specs** - Update status and document decisions
 
 ## When to Use Specs
 
-Write a spec for:
+**Write a spec for:**
 - Features affecting multiple parts of the system
 - Breaking changes or significant refactors
 - Design decisions needing team alignment
 
-Skip specs for:
+**Skip specs for:**
 - Bug fixes
 - Trivial changes
 - Self-explanatory refactors
 
-## Essential Commands
-
-**Quick Reference** (for full details, see `lean-spec --help`):
-
-**Discovery:**
-- `lean-spec list` - See all specs
-- `lean-spec search "<query>"` - Find relevant specs
-
-**Working with specs:**
-- `lean-spec create <name>` - Create new spec
-- `lean-spec update <spec> --status <status>` - Update status (REQUIRED - never edit frontmatter manually)
-- `lean-spec update <spec> --priority <priority>` - Update priority
-- `lean-spec deps <spec>` - Show dependency graph
-- `lean-spec tokens <spec>` - Count tokens for context management
-
-**Project overview:**
-- `lean-spec board` - Kanban view with project health
-- `lean-spec stats` - Quick project metrics
-
-**When in doubt:** Run `lean-spec --help` or `lean-spec <command> --help` to discover commands.
-
 ## Spec Relationships
 
-LeanSpec has two types of relationships:
-
 ### `related` - Bidirectional Soft Reference
-Informational relationship between specs. Automatically shown from both sides.
-
-**Use when:** Specs cover related topics, work is coordinated but not blocking.
+Informational relationship between specs. Shown from both sides.
+**Use when:** Related topics, coordinated but not blocking work.
 
 ### `depends_on` - Directional Blocking Dependency
 Hard dependency - spec cannot start until dependencies complete.
+**Use when:** True blocking dependency, work order matters.
 
-**Use when:** Spec truly cannot start until another completes, work order matters.
-
-**Best Practice:** Use `related` by default. Reserve `depends_on` for true blocking dependencies.
-
-## SDD Workflow
-
-1. **Discover** - Check existing specs with `lean-spec list`
-2. **Plan** - Create spec with `lean-spec create <name>` (status: `planned`)
-3. **Start Work** - Run `lean-spec update <spec> --status in-progress` before implementing
-4. **Implement** - Write code/docs, keep spec in sync as you learn
-5. **Complete** - Run `lean-spec update <spec> --status complete` after implementation done
-6. **Document** - Report progress and document changes into the spec
-
-**CRITICAL - What "Work" Means:**
-- ❌ **NOT**: Creating/writing the spec document itself
-- ✅ **YES**: Implementing what the spec describes (code, docs, features, etc.)
-
-**Frontmatter Editing Rules:**
-- **NEVER manually edit**: `status`, `priority`, `tags`, `assignee`, `transitions`, timestamps, `depends_on`, `related`
-- **Use CLI commands**: `lean-spec update`, `lean-spec link`, `lean-spec unlink`
-
-**Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old/stale specs to `archived/` directory.
+**Default:** Use `related`. Reserve `depends_on` for true blockers.
 
 ## Quality Standards
 
-- Code is clear and maintainable
-- Tests cover critical paths
-- Specs stay in sync with implementation
 - **Status tracking is mandatory:**
-  - Specs start as `planned` after creation
-  - Mark `in-progress` BEFORE starting implementation work
-  - Mark `complete` AFTER implementation is finished
-  - **Remember**: Status tracks implementation, not spec document completion
-  - Never leave specs with stale status
+  - `planned` → after creation
+  - `in-progress` → BEFORE starting implementation
+  - `complete` → AFTER finishing implementation
+- Specs stay in sync with implementation
+- Never leave specs with stale status
 
 ## Spec Complexity Guidelines
 
-**Token Thresholds:**
-- **<2,000 tokens**: ✅ Optimal
-- **2,000-3,500 tokens**: ✅ Good
-- **3,500-5,000 tokens**: ⚠️ Warning - Consider splitting
-- **>5,000 tokens**: 🔴 Should split
-
-**Check with:** `lean-spec tokens <spec>`
-
-**When to split:** >3,500 tokens, multiple concerns, takes >10 min to read
+| Tokens | Status |
+|--------|--------|
+| <2,000 | ✅ Optimal |
+| 2,000-3,500 | ✅ Good |
+| 3,500-5,000 | ⚠️ Consider splitting |
+| >5,000 | 🔴 Should split |
 
-**How to split:** Use sub-specs or split into related specs with `lean-spec link --related`
+Use `tokens` tool to check spec size.
 
 ---
 
-**Remember**: LeanSpec is a mindset, not a rulebook. When in doubt, keep it simple and use `lean-spec --help` to discover features as needed.
+**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!

package/templates/standard/AGENTS.md

@@ -2,112 +2,157 @@
 
 ## Project: {project_name}
 
-Lightweight spec methodology for AI-powered development.
+<!-- ═══════════════════════════════════════════════════════════════════════════
+     👇 TODO: Fill in your project context below (then delete these comments)
+     ═══════════════════════════════════════════════════════════════════════════ -->
+
+### 📋 Project Context
+
+**What this project does:**
+_TODO: Describe your project in 1-2 sentences_
+
+**Tech stack:**
+_TODO: List main technologies (e.g., Node.js, React, PostgreSQL)_
+
+**Key objectives:**
+_TODO: What are you building toward? (e.g., Launch MVP by Q1)_
+
+<!-- ═══════════════════════════════════════════════════════════════════════════
+     👆 End of TODO section - Delete these comment markers when done
+     ═══════════════════════════════════════════════════════════════════════════ -->
+
+## 🚨 CRITICAL: Before ANY Task
+
+**STOP and check these first:**
+
+1. **Discover context** → Use `board` tool to see project state
+2. **Search for related work** → Use `search` tool before creating new specs
+3. **Never create files manually** → Always use `create` tool for new specs
+
+> **Why?** Skipping discovery creates duplicate work. Manual file creation breaks LeanSpec tooling.
+
+## 🔧 How to Manage Specs
+
+### Primary Method: MCP Tools (Recommended)
+
+If you have LeanSpec MCP tools available, **ALWAYS use them**:
+
+| Action | MCP Tool | Description |
+|--------|----------|-------------|
+| See project status | `board` | Kanban view + project health metrics |
+| List all specs | `list` | Filterable list with metadata |
+| Search specs | `search` | Semantic search across all content |
+| View a spec | `view` | Full content with formatting |
+| Create new spec | `create` | Auto-sequences, proper structure |
+| Update spec | `update` | Validates transitions, timestamps |
+| Check dependencies | `deps` | Visual dependency graph |
+
+**Why MCP over CLI?**
+- ✅ Direct tool integration (no shell execution needed)
+- ✅ Structured responses (better for AI reasoning)
+- ✅ Real-time validation (immediate feedback)
+- ✅ Context-aware (understands project state)
+
+### Fallback: CLI Commands
+
+If MCP tools are not available, use CLI commands:
+
+```bash
+lean-spec board              # Project overview
+lean-spec list               # See all specs
+lean-spec search "query"     # Find relevant specs
+lean-spec create <name>      # Create new spec
+lean-spec update <spec> --status <status>  # Update status
+lean-spec deps <spec>        # Show dependencies
+```
+
+**Tip:** Check if you have LeanSpec MCP tools available before using CLI.
+
+## ⚠️ SDD Workflow Checkpoints
+
+### Before Starting ANY Task
+
+1. 📋 **Run `board`** - What's the current project state?
+2. 🔍 **Run `search`** - Are there related specs already?
+3. 📝 **Check existing specs** - Is there one for this work?
+
+### During Implementation
+
+4. 📊 **Update status to `in-progress`** BEFORE coding
+5. 📝 **Document decisions** in the spec as you work
+6. 🔗 **Link related specs** if you discover connections
+
+### After Completing Work
+
+7. ✅ **Update status to `complete`** when done
+8. 📄 **Document what you learned** in the spec
+9. 🤔 **Create follow-up specs** if needed
+
+### 🚫 Common Mistakes to Avoid
+
+| ❌ Don't | ✅ Do Instead |
+|----------|---------------|
+| Create spec files manually | Use `create` tool |
+| Skip discovery before new work | Run `board` and `search` first |
+| Leave status as "planned" after starting | Update to `in-progress` immediately |
+| Finish work without updating spec | Document decisions, update status |
+| Edit frontmatter manually | Use `update` tool |
+| Forget about specs mid-conversation | Check spec status periodically |
 
 ## Core Rules
 
 1. **Read README.md first** - Understand project context
 2. **Check specs/** - Review existing specs before starting
-3. **Use `lean-spec --help`** - When unsure about commands, check the built-in help
+3. **Use MCP tools** - Prefer MCP over CLI when available
 4. **Follow LeanSpec principles** - Clarity over documentation
 5. **Keep it minimal** - If it doesn't add clarity, cut it
-6. **NEVER manually edit system-managed frontmatter** - Fields like `status`, `priority`, `tags`, `assignee`, `transitions`, `created_at`, `updated_at`, `completed_at`, `depends_on`, `related` are system-managed. Always use `lean-spec update`, `lean-spec link`, `lean-spec unlink`, or `lean-spec create` commands. Manual edits will cause metadata corruption and tracking issues.
-7. **Never use nested code blocks** - Markdown doesn't support code blocks within code blocks. If you need to show code examples in documentation, use indentation or describe the structure instead of nesting backticks.
+6. **NEVER manually edit frontmatter** - Use `update`, `link`, `unlink` tools
+7. **Track progress in specs** - Update status and document decisions
 
 ## When to Use Specs
 
-Write a spec for:
+**Write a spec for:**
 - Features affecting multiple parts of the system
 - Breaking changes or significant refactors
 - Design decisions needing team alignment
 
-Skip specs for:
+**Skip specs for:**
 - Bug fixes
 - Trivial changes
 - Self-explanatory refactors
 
-## Essential Commands
-
-**Quick Reference** (for full details, see `lean-spec --help`):
-
-**Discovery:**
-- `lean-spec list` - See all specs
-- `lean-spec search "<query>"` - Find relevant specs
-
-**Working with specs:**
-- `lean-spec create <name>` - Create new spec
-- `lean-spec update <spec> --status <status>` - Update status (REQUIRED - never edit frontmatter manually)
-- `lean-spec update <spec> --priority <priority>` - Update priority
-- `lean-spec deps <spec>` - Show dependency graph
-- `lean-spec tokens <spec>` - Count tokens for context management
-
-**Project overview:**
-- `lean-spec board` - Kanban view with project health
-- `lean-spec stats` - Quick project metrics
-
-**When in doubt:** Run `lean-spec --help` or `lean-spec <command> --help` to discover commands.
-
 ## Spec Relationships
 
-LeanSpec has two types of relationships:
-
 ### `related` - Bidirectional Soft Reference
-Informational relationship between specs. Automatically shown from both sides.
-
-**Use when:** Specs cover related topics, work is coordinated but not blocking.
+Informational relationship between specs. Shown from both sides.
+**Use when:** Related topics, coordinated but not blocking work.
 
 ### `depends_on` - Directional Blocking Dependency
 Hard dependency - spec cannot start until dependencies complete.
+**Use when:** True blocking dependency, work order matters.
 
-**Use when:** Spec truly cannot start until another completes, work order matters.
-
-**Best Practice:** Use `related` by default. Reserve `depends_on` for true blocking dependencies.
-
-## SDD Workflow
-
-1. **Discover** - Check existing specs with `lean-spec list`
-2. **Plan** - Create spec with `lean-spec create <name>` (status: `planned`)
-3. **Start Work** - Run `lean-spec update <spec> --status in-progress` before implementing
-4. **Implement** - Write code/docs, keep spec in sync as you learn
-5. **Complete** - Run `lean-spec update <spec> --status complete` after implementation done
-6. **Document** - Report progress and document changes into the spec
-
-**CRITICAL - What "Work" Means:**
-- ❌ **NOT**: Creating/writing the spec document itself
-- ✅ **YES**: Implementing what the spec describes (code, docs, features, etc.)
-
-**Frontmatter Editing Rules:**
-- **NEVER manually edit**: `status`, `priority`, `tags`, `assignee`, `transitions`, timestamps, `depends_on`, `related`
-- **Use CLI commands**: `lean-spec update`, `lean-spec link`, `lean-spec unlink`
-
-**Note on Archiving**: Archive specs when they're no longer actively referenced (weeks/months after completion), not immediately. Use `lean-spec archive <spec>` to move old/stale specs to `archived/` directory.
+**Default:** Use `related`. Reserve `depends_on` for true blockers.
 
 ## Quality Standards
 
-- Code is clear and maintainable
-- Tests cover critical paths
-- Specs stay in sync with implementation
 - **Status tracking is mandatory:**
-  - Specs start as `planned` after creation
-  - Mark `in-progress` BEFORE starting implementation work
-  - Mark `complete` AFTER implementation is finished
-  - **Remember**: Status tracks implementation, not spec document completion
-  - Never leave specs with stale status
+  - `planned` → after creation
+  - `in-progress` → BEFORE starting implementation
+  - `complete` → AFTER finishing implementation
+- Specs stay in sync with implementation
+- Never leave specs with stale status
 
 ## Spec Complexity Guidelines
 
-**Token Thresholds:**
-- **<2,000 tokens**: ✅ Optimal
-- **2,000-3,500 tokens**: ✅ Good
-- **3,500-5,000 tokens**: ⚠️ Warning - Consider splitting
-- **>5,000 tokens**: 🔴 Should split
-
-**Check with:** `lean-spec tokens <spec>`
-
-**When to split:** >3,500 tokens, multiple concerns, takes >10 min to read
+| Tokens | Status |
+|--------|--------|
+| <2,000 | ✅ Optimal |
+| 2,000-3,500 | ✅ Good |
+| 3,500-5,000 | ⚠️ Consider splitting |
+| >5,000 | 🔴 Should split |
 
-**How to split:** Use sub-specs or split into related specs with `lean-spec link --related`
+Use `tokens` tool to check spec size.
 
 ---
 
-**Remember**: LeanSpec is a mindset, not a rulebook. When in doubt, keep it simple and use `lean-spec --help` to discover features as needed.
+**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!