ultra-builder-pro-cli 0.13.0 → 0.14.0

package/orchestrator/planner/expand-prompt.cjs

@@ -1,62 +0,0 @@
-'use strict';
-
-// Phase 8A.3 — Prompt templates for task → subtasks expansion.
-//
-// Parent context (title, type, priority, complexity, files_modified) is
-// serialized into the user prompt so the LLM can produce children aligned
-// with the parent's shape. sub_count defaults to 3 when omitted.
-
-const DEFAULT_SUB_COUNT = 3;
-
-function buildExpandSystemPrompt({ sub_count = DEFAULT_SUB_COUNT } = {}) {
-  return `You are an engineering task decomposer. Break a single complex task into ${sub_count} smaller subtasks that together deliver the parent's scope.
-
-Output STRICT JSON matching this shape — nothing else, no markdown fences, no prose:
-
-{
-  "children": [
-    {
-      "id": "child-1",
-      "title": "Imperative short title (3-80 chars)",
-      "type": "architecture | feature | bugfix",
-      "priority": "P0 | P1 | P2 | P3",
-      "complexity": 1-10,
-      "deps": ["child-2"],
-      "files_modified": ["src/path/to/file.ts"]
-    }
-  ]
-}
-
-Rules:
-- Exactly ${sub_count} children.
-- Each id matches /^[a-zA-Z0-9_\\-]+$/ and is unique in the list.
-- "deps" references siblings in the same list; omit or use [] when none.
-- "files_modified" overlaps with the parent's files_modified where possible.
-- Each child's complexity is < parent's complexity; sum should approximate the parent.
-- Return JSON only.`;
-}
-
-function buildExpandUserPrompt(parent) {
-  const files = Array.isArray(parent.files_modified) ? parent.files_modified : [];
-  const deps = Array.isArray(parent.deps) ? parent.deps : [];
-  return [
-    'Parent task to decompose:',
-    '',
-    `- id: ${parent.id}`,
-    `- title: ${parent.title}`,
-    `- type: ${parent.type}`,
-    `- priority: ${parent.priority}`,
-    parent.complexity != null ? `- complexity: ${parent.complexity}` : null,
-    files.length ? `- files_modified: ${JSON.stringify(files)}` : null,
-    deps.length ? `- existing deps: ${JSON.stringify(deps)}` : null,
-    parent.trace_to ? `- trace_to: ${parent.trace_to}` : null,
-    '',
-    'Return the children list as JSON following the system schema.',
-  ].filter((l) => l !== null).join('\n');
-}
-
-module.exports = {
-  buildExpandSystemPrompt,
-  buildExpandUserPrompt,
-  DEFAULT_SUB_COUNT,
-};

package/orchestrator/planner/expand-prompt.test.cjs

@@ -1,52 +0,0 @@
-'use strict';
-
-const test = require('node:test');
-const assert = require('node:assert/strict');
-
-const {
-  buildExpandSystemPrompt,
-  buildExpandUserPrompt,
-  DEFAULT_SUB_COUNT,
-} = require('./expand-prompt.cjs');
-
-test('buildExpandSystemPrompt: mentions sub_count explicitly', () => {
-  const s = buildExpandSystemPrompt({ sub_count: 4 });
-  assert.match(s, /Exactly 4 children/);
-  assert.match(s, /STRICT JSON/);
-});
-
-test('buildExpandSystemPrompt: falls back to DEFAULT_SUB_COUNT when omitted', () => {
-  const s = buildExpandSystemPrompt({});
-  assert.match(s, new RegExp(`Exactly ${DEFAULT_SUB_COUNT} children`));
-});
-
-test('buildExpandUserPrompt: serializes parent fields into prompt body', () => {
-  const parent = {
-    id: 'parent-1',
-    title: 'Build search feature',
-    type: 'feature',
-    priority: 'P1',
-    complexity: 8,
-    files_modified: ['src/search/index.ts', 'src/search/query.ts'],
-    deps: ['infra-1'],
-    trace_to: 'spec §3.2',
-  };
-  const body = buildExpandUserPrompt(parent);
-  assert.match(body, /parent-1/);
-  assert.match(body, /Build search feature/);
-  assert.match(body, /complexity: 8/);
-  assert.match(body, /src\/search\/index\.ts/);
-  assert.match(body, /infra-1/);
-  assert.match(body, /spec §3\.2/);
-});
-
-test('buildExpandUserPrompt: omits empty optional fields', () => {
-  const parent = {
-    id: 'p', title: 'Tiny task', type: 'feature', priority: 'P3',
-    complexity: null, files_modified: [], deps: [],
-  };
-  const body = buildExpandUserPrompt(parent);
-  assert.doesNotMatch(body, /files_modified/);
-  assert.doesNotMatch(body, /existing deps/);
-  assert.doesNotMatch(body, /complexity:/);
-});

package/orchestrator/planner/prd-prompt.cjs

@@ -1,44 +0,0 @@
-'use strict';
-
-// Phase 8A.1 — Prompt templates for PRD → task-list parsing.
-//
-// Kept in a dedicated module so downstream evaluation (fixture regression,
-// prompt A/B testing) can diff the template against commits without touching
-// parser logic.
-
-const SYSTEM_PROMPT = `You are an engineering planner. Decompose a product requirement document (PRD) into a topologically ordered task list that a coding agent can execute sequentially or in parallel.
-
-Output STRICT JSON matching this shape — nothing else, no markdown fences, no prose:
-
-{
-  "tasks": [
-    {
-      "id": "task-1",
-      "title": "Imperative short title (3-80 chars)",
-      "type": "architecture | feature | bugfix",
-      "priority": "P0 | P1 | P2 | P3",
-      "complexity": 1-10,
-      "deps": ["task-2"],
-      "files_modified": ["src/path/to/file.ts"]
-    }
-  ]
-}
-
-Rules:
-- Every task id matches /^task-[0-9]+$/ and is unique in the list.
-- "deps" references other ids in the same list; omit or use [] when none.
-- "files_modified" is your best guess of affected paths; use [] when unsure.
-- "complexity" 1 = trivial, 10 = multi-day. Tasks at 7+ will be auto-expanded later.
-- "priority" — P0 blocks other work, P1 critical path, P2 standard, P3 nice-to-have.
-- "type" — architecture for design/scaffolding, feature for new capability, bugfix for correcting existing behaviour.
-- Return JSON only. No surrounding text, no trailing explanation.`;
-
-function buildSystemPrompt() {
-  return SYSTEM_PROMPT;
-}
-
-function buildUserPrompt(prdText) {
-  return `PRD:\n\n${prdText}\n\nReturn the task list as JSON following the system schema.`;
-}
-
-module.exports = { SYSTEM_PROMPT, buildSystemPrompt, buildUserPrompt };

package/orchestrator/planner/prd-prompt.test.cjs

@@ -1,30 +0,0 @@
-'use strict';
-
-const test = require('node:test');
-const assert = require('node:assert/strict');
-
-const {
-  SYSTEM_PROMPT,
-  buildSystemPrompt,
-  buildUserPrompt,
-} = require('./prd-prompt.cjs');
-
-test('buildSystemPrompt returns the module-level template', () => {
-  assert.equal(buildSystemPrompt(), SYSTEM_PROMPT);
-  assert.match(SYSTEM_PROMPT, /engineering planner/i);
-  assert.match(SYSTEM_PROMPT, /STRICT JSON/);
-  assert.match(SYSTEM_PROMPT, /\/\^task-\[0-9\]\+\$\//);
-});
-
-test('buildUserPrompt embeds PRD text verbatim', () => {
-  const prd = 'As a user I want to search products by keyword';
-  const out = buildUserPrompt(prd);
-  assert.ok(out.includes(prd), 'user prompt must contain the PRD text');
-  assert.match(out, /JSON/);
-});
-
-test('buildUserPrompt tolerates long PRD text without truncation', () => {
-  const long = 'line\n'.repeat(500);
-  const out = buildUserPrompt(long);
-  assert.ok(out.includes(long));
-});