backlog-compiler

Backlog Compiler

Converts an existing spec (PRD, ticket, or freeform feature description) into .code-virtuoso/loop/backlog.json - the committed plan that iteration-loop executes one step at a time, with completion gated by an objective verifyCommand, never by self-report. Each item is a sequence of steps; a simple item is a single step.

Step 0: Reuse saved project settings

Before asking the user anything, read the merged Code Virtuoso config (spec/config-spec.md): the user file ($CODE_VIRTUOSO_CONFIG_HOME/config.json, else ${XDG_CONFIG_HOME:-$HOME/.config}/code-virtuoso/config.json), then <git root>/.code-virtuoso/config.json, then <git root>/.code-virtuoso/config.local.json. Later files win; objects merge, arrays and scalars replace. Missing files are normal.

root=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
home="${CODE_VIRTUOSO_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/code-virtuoso}"
files=(); for f in "$home/config.json" "$root/.code-virtuoso/config.json" "$root/.code-virtuoso/config.local.json"; do [ -f "$f" ] && files+=("$f"); done
[ ${#files[@]} -gt 0 ] && jq -s 'reduce .[] as $x ({}; . * $x)' "${files[@]}" || echo '{}'

Two namespaces matter here:

• ticket-delivery: commands.test and commands.staticAnalysis answer the test and static analysis questions below; branchPattern, ticketIdPattern and mainBranch shape the branch (Step 1). The legacy ticket-delivery supplement file is not read here; if the namespace is empty, run the ticket-delivery setup once to save it.
• loop: defaults for config in Step 6 (maxIterations, permissionMode, allowedTools, allowedPaths, protectedPaths, and the other limits). Seed the backlog's config from these values instead of the table in Step 6. Never save a credential there.

For each answer the config does not give, ask the user directly:

1. What command runs the test suite for a single file/class (the answer becomes the basis for each step's verifyCommand)?
2. What command runs static analysis / type-checking, if any (append to verifyCommand with &&)?
3. Which directories or files must never be modified by the loop (test directories, CI config, fixtures) - these become config.protectedPaths?
4. Primary stack, to pick a sensible config.allowedTools base (see Step 6).