lean-spec 0.2.7 → 0.2.9-dev.20251205030455

package/dist/cli.js

@@ -1,5 +1,8 @@
-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-Q6B3LVO7.js';
-import './chunk-LVD7ZAVZ.js';
+import { agentCommand, analyzeCommand, archiveCommand, boardCommand, checkCommand, compactCommand, createCommand, depsCommand, examplesCommand, filesCommand, ganttCommand, initCommand, linkCommand, listCommand, mcpCommand, migrateCommand, openCommand, searchCommand, splitCommand, statsCommand, templatesCommand, timelineCommand, tokensCommand, uiCommand, unlinkCommand, updateCommand, viewCommand } from './chunk-BJHJ6IUO.js';
+import { backfillCommand } from './chunk-H5MCUMBK.js';
+import { validateCommand } from './chunk-CJMVV46H.js';
+import './chunk-RF5PKL6L.js';
+import './chunk-VN5BUHTV.js';
 import { Command } from 'commander';
 import { readFileSync } from 'fs';
 import { fileURLToPath } from 'url';
@@ -102,7 +105,6 @@ Examples:
   $ lean-spec list --status in-progress
   $ lean-spec view 042
   $ lean-spec link 085 --depends-on 042,035
-  $ lean-spec link 085 --related 082
   $ lean-spec unlink 085 --depends-on 042
   $ lean-spec deps 085
   $ lean-spec backfill --dry-run

package/dist/cli.js.map

@@ -1 +1 @@
-{"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"]}
+{"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,CAyE5B,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 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/{frontmatter-R2DANL5X.js → frontmatter-6ZBAGOEU.js}

@@ -1,3 +1,3 @@
-export { enrichWithTimestamps, getSpecFile, matchesFilter, normalizeDateFields, normalizeTagsField, parseFrontmatter, updateFrontmatter, validateCustomField, validateCustomFields } from './chunk-LVD7ZAVZ.js';
-//# sourceMappingURL=frontmatter-R2DANL5X.js.map
-//# sourceMappingURL=frontmatter-R2DANL5X.js.map
+export { enrichWithTimestamps, getSpecFile, matchesFilter, normalizeDateFields, normalizeTagsField, parseFrontmatter, updateFrontmatter, validateCustomField, validateCustomFields } from './chunk-VN5BUHTV.js';
+//# sourceMappingURL=frontmatter-6ZBAGOEU.js.map
+//# sourceMappingURL=frontmatter-6ZBAGOEU.js.map

package/dist/{frontmatter-R2DANL5X.js.map → frontmatter-6ZBAGOEU.js.map}

@@ -1 +1 @@
-{"version":3,"sources":[],"names":[],"mappings":"","file":"frontmatter-R2DANL5X.js"}
+{"version":3,"sources":[],"names":[],"mappings":"","file":"frontmatter-6ZBAGOEU.js"}

package/dist/mcp-server.js

@@ -1,5 +1,8 @@
 #!/usr/bin/env node
-export { createMcpServer } from './chunk-Q6B3LVO7.js';
-import './chunk-LVD7ZAVZ.js';
+export { createMcpServer } from './chunk-BJHJ6IUO.js';
+import './chunk-H5MCUMBK.js';
+import './chunk-CJMVV46H.js';
+import './chunk-RF5PKL6L.js';
+import './chunk-VN5BUHTV.js';
 //# sourceMappingURL=mcp-server.js.map
 //# sourceMappingURL=mcp-server.js.map

package/dist/validate-DIWYTDEF.js

@@ -0,0 +1,5 @@
+export { validateCommand, validateSpecs } from './chunk-CJMVV46H.js';
+import './chunk-RF5PKL6L.js';
+import './chunk-VN5BUHTV.js';
+//# sourceMappingURL=validate-DIWYTDEF.js.map
+//# sourceMappingURL=validate-DIWYTDEF.js.map

package/dist/validate-DIWYTDEF.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"names":[],"mappings":"","file":"validate-DIWYTDEF.js"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lean-spec",
-  "version": "0.2.7",
+  "version": "0.2.9-dev.20251205030455",
   "description": "Specification-driven development made simple",
   "type": "module",
   "bin": {
@@ -67,7 +67,7 @@
     "zod": "^3.25.76"
   },
   "devDependencies": {
-    "@leanspec/core": "^0.2.7",
+    "@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,25 +2,6 @@
 
 ## Project: {project_name}
 
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     👇 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:**
@@ -31,128 +12,86 @@ _TODO: What are you building toward? (e.g., Launch MVP by Q1)_
 
 > **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
-```
+## 🔧 Managing Specs
 
-**Tip:** Check if you have LeanSpec MCP tools available before using CLI.
+### MCP Tools (Preferred) with CLI Fallback
 
-## ⚠️ SDD Workflow Checkpoints
+| Action | MCP Tool | CLI Fallback |
+|--------|----------|--------------|
+| Project status | `board` | `lean-spec board` |
+| List specs | `list` | `lean-spec list` |
+| Search specs | `search` | `lean-spec search "query"` |
+| View spec | `view` | `lean-spec view <spec>` |
+| Create spec | `create` | `lean-spec create <name>` |
+| Update spec | `update` | `lean-spec update <spec> --status <status>` |
+| Link specs | `link` | `lean-spec link <spec> --depends-on <other>` |
+| Unlink specs | `unlink` | `lean-spec unlink <spec> --depends-on <other>` |
+| Dependencies | `deps` | `lean-spec deps <spec>` |
+| Token count | `tokens` | `lean-spec tokens <spec>` |
 
-### Before Starting ANY Task
+## ⚠️ Core Rules
 
-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?
+| Rule | Details |
+|------|---------|
+| **NEVER edit frontmatter manually** | Use `update`, `link`, `unlink` for: `status`, `priority`, `tags`, `assignee`, `transitions`, timestamps, `depends_on` |
+| **ALWAYS link spec references** | Content mentions another spec → `lean-spec link <spec> --depends-on <other>` |
+| **Track status transitions** | `planned` → `in-progress` (before coding) → `complete` (after done) |
+| **No nested code blocks** | Use indentation instead |
 
-### 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
+### 🚫 Common Mistakes
 
 | ❌ 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 |
+| Skip discovery | Run `board` and `search` first |
+| Leave status as "planned" | Update to `in-progress` before coding |
 | 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 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 frontmatter** - Use `update`, `link`, `unlink` tools
-7. **Track progress in specs** - Update status and document decisions
-
-## When to Use Specs
 
-**Write a spec for:**
-- Features affecting multiple parts of the system
-- Breaking changes or significant refactors
-- Design decisions needing team alignment
+## 📋 SDD Workflow
 
-**Skip specs for:**
-- Bug fixes
-- Trivial changes
-- Self-explanatory refactors
+```
+BEFORE: board → search → check existing specs
+DURING: update status to in-progress → code → document decisions → link dependencies
+AFTER:  update status to complete → document learnings
+```
 
-## Spec Relationships
+**Status tracks implementation, NOT spec writing.**
 
-### `related` - Bidirectional Soft Reference
-Informational relationship between specs. Shown from both sides.
-**Use when:** Related topics, coordinated but not blocking work.
+## Spec Dependencies
 
-### `depends_on` - Directional Blocking Dependency
-Hard dependency - spec cannot start until dependencies complete.
-**Use when:** True blocking dependency, work order matters.
+Use `depends_on` to express blocking relationships between specs:
+- **`depends_on`** = True blocker, work order matters, directional (A depends on B)
 
-**Default:** Use `related`. Reserve `depends_on` for true blockers.
+Link dependencies when one spec builds on another:
+```bash
+lean-spec link <spec> --depends-on <other-spec>
+```
 
-## Quality Standards
+## When to Use Specs
 
-- **Status tracking is mandatory:**
-  - `planned` → after creation
-  - `in-progress` → BEFORE starting implementation
-  - `complete` → AFTER finishing implementation
-- Specs stay in sync with implementation
-- Never leave specs with stale status
+| ✅ Write spec | ❌ Skip spec |
+|---------------|--------------|
+| Multi-part features | Bug fixes |
+| Breaking changes | Trivial changes |
+| Design decisions | Self-explanatory refactors |
 
-## Spec Complexity Guidelines
+## Token Thresholds
 
 | Tokens | Status |
 |--------|--------|
 | <2,000 | ✅ Optimal |
 | 2,000-3,500 | ✅ Good |
 | 3,500-5,000 | ⚠️ Consider splitting |
-| >5,000 | 🔴 Should split |
+| >5,000 | 🔴 Must split |
+
+## First Principles (Priority Order)
 
-Use `tokens` tool to check spec size.
+1. **Context Economy** - <2,000 tokens optimal, >3,500 needs splitting
+2. **Signal-to-Noise** - Every word must inform a decision
+3. **Intent Over Implementation** - Capture why, let how emerge
+4. **Bridge the Gap** - Both human and AI must understand
+5. **Progressive Disclosure** - Add complexity only when pain is felt
 
 ---
 
-**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!
+**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!

package/templates/detailed/README.md

@@ -22,7 +22,7 @@ Keep it lean, but organized. Use sub-specs to manage complexity without overwhel
 
 ## Next Steps
 
-1. Customize AGENTS.md for your project
-2. Create your first spec: `lean-spec create my-feature`
-3. When a spec grows large, split sections into sub-spec files
+You're ready to go! Ask your AI to create a spec for your next feature.
+
+When a spec grows large, consider splitting sections into sub-spec files.
 

package/templates/examples/api-refactor/README.md

@@ -1,6 +1,6 @@
 # API Refactor Demo
 
-> **Tutorial**: [Refactoring with Specs](https://leanspec.dev/docs/tutorials/refactoring-specs)
+> **Tutorial**: [Refactoring with Specs](https://lean-spec.dev/docs/tutorials/refactoring-specs)
 
 ## Scenario
 

package/templates/examples/dark-theme/README.md

@@ -1,6 +1,6 @@
 # Dark Theme Demo
 
-> **Tutorial**: [Adding Dark Theme Support](https://leanspec.dev/docs/tutorials/adding-dark-theme)
+> **Tutorial**: [Adding Dark Theme Support](https://lean-spec.dev/docs/tutorials/adding-dark-theme)
 
 ## Scenario
 

package/templates/examples/dashboard-widgets/README.md

@@ -1,6 +1,6 @@
 # Dashboard Widgets Demo
 
-> **Tutorial**: [Managing Multiple Features](https://leanspec.dev/docs/tutorials/multiple-features)
+> **Tutorial**: [Managing Multiple Features](https://lean-spec.dev/docs/tutorials/multiple-features)
 
 ## Scenario
 

package/templates/standard/AGENTS.md

@@ -2,25 +2,6 @@
 
 ## Project: {project_name}
 
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     👇 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:**
@@ -31,128 +12,86 @@ _TODO: What are you building toward? (e.g., Launch MVP by Q1)_
 
 > **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
-```
+## 🔧 Managing Specs
 
-**Tip:** Check if you have LeanSpec MCP tools available before using CLI.
+### MCP Tools (Preferred) with CLI Fallback
 
-## ⚠️ SDD Workflow Checkpoints
+| Action | MCP Tool | CLI Fallback |
+|--------|----------|--------------|
+| Project status | `board` | `lean-spec board` |
+| List specs | `list` | `lean-spec list` |
+| Search specs | `search` | `lean-spec search "query"` |
+| View spec | `view` | `lean-spec view <spec>` |
+| Create spec | `create` | `lean-spec create <name>` |
+| Update spec | `update` | `lean-spec update <spec> --status <status>` |
+| Link specs | `link` | `lean-spec link <spec> --depends-on <other>` |
+| Unlink specs | `unlink` | `lean-spec unlink <spec> --depends-on <other>` |
+| Dependencies | `deps` | `lean-spec deps <spec>` |
+| Token count | `tokens` | `lean-spec tokens <spec>` |
 
-### Before Starting ANY Task
+## ⚠️ Core Rules
 
-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?
+| Rule | Details |
+|------|---------|
+| **NEVER edit frontmatter manually** | Use `update`, `link`, `unlink` for: `status`, `priority`, `tags`, `assignee`, `transitions`, timestamps, `depends_on` |
+| **ALWAYS link spec references** | Content mentions another spec → `lean-spec link <spec> --depends-on <other>` |
+| **Track status transitions** | `planned` → `in-progress` (before coding) → `complete` (after done) |
+| **No nested code blocks** | Use indentation instead |
 
-### 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
+### 🚫 Common Mistakes
 
 | ❌ 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 |
+| Skip discovery | Run `board` and `search` first |
+| Leave status as "planned" | Update to `in-progress` before coding |
 | 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 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 frontmatter** - Use `update`, `link`, `unlink` tools
-7. **Track progress in specs** - Update status and document decisions
-
-## When to Use Specs
 
-**Write a spec for:**
-- Features affecting multiple parts of the system
-- Breaking changes or significant refactors
-- Design decisions needing team alignment
+## 📋 SDD Workflow
 
-**Skip specs for:**
-- Bug fixes
-- Trivial changes
-- Self-explanatory refactors
+```
+BEFORE: board → search → check existing specs
+DURING: update status to in-progress → code → document decisions → link dependencies
+AFTER:  update status to complete → document learnings
+```
 
-## Spec Relationships
+**Status tracks implementation, NOT spec writing.**
 
-### `related` - Bidirectional Soft Reference
-Informational relationship between specs. Shown from both sides.
-**Use when:** Related topics, coordinated but not blocking work.
+## Spec Dependencies
 
-### `depends_on` - Directional Blocking Dependency
-Hard dependency - spec cannot start until dependencies complete.
-**Use when:** True blocking dependency, work order matters.
+Use `depends_on` to express blocking relationships between specs:
+- **`depends_on`** = True blocker, work order matters, directional (A depends on B)
 
-**Default:** Use `related`. Reserve `depends_on` for true blockers.
+Link dependencies when one spec builds on another:
+```bash
+lean-spec link <spec> --depends-on <other-spec>
+```
 
-## Quality Standards
+## When to Use Specs
 
-- **Status tracking is mandatory:**
-  - `planned` → after creation
-  - `in-progress` → BEFORE starting implementation
-  - `complete` → AFTER finishing implementation
-- Specs stay in sync with implementation
-- Never leave specs with stale status
+| ✅ Write spec | ❌ Skip spec |
+|---------------|--------------|
+| Multi-part features | Bug fixes |
+| Breaking changes | Trivial changes |
+| Design decisions | Self-explanatory refactors |
 
-## Spec Complexity Guidelines
+## Token Thresholds
 
 | Tokens | Status |
 |--------|--------|
 | <2,000 | ✅ Optimal |
 | 2,000-3,500 | ✅ Good |
 | 3,500-5,000 | ⚠️ Consider splitting |
-| >5,000 | 🔴 Should split |
+| >5,000 | 🔴 Must split |
+
+## First Principles (Priority Order)
 
-Use `tokens` tool to check spec size.
+1. **Context Economy** - <2,000 tokens optimal, >3,500 needs splitting
+2. **Signal-to-Noise** - Every word must inform a decision
+3. **Intent Over Implementation** - Capture why, let how emerge
+4. **Bridge the Gap** - Both human and AI must understand
+5. **Progressive Disclosure** - Add complexity only when pain is felt
 
 ---
 
-**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!
+**Remember:** LeanSpec tracks what you're building. Keep specs in sync with your work!

package/templates/standard/README.md

@@ -21,6 +21,5 @@ Keep it lean. Write specs for features that need clarity. Skip them for obvious
 
 ## Next Steps
 
-1. Customize AGENTS.md for your project
-2. Create your first spec: `lean-spec create my-feature`
+You're ready to go! Ask your AI to create a spec for your next feature.