/apply

Run the full spec-tree TDD flow (contextualize, architect, test, code — with audit gates) and commit.

Three modes:

1. With node path (/apply some/node): Run TDD on the given subtree, then stop.
2. Without argument: Determine work from conversation context. If nothing is clear, fall back to spx/EXCLUDE — nodes with specs and tests but no implementation.
3. With --agent (/apply --agent some/node): Launch the applier subagent to run the full flow autonomously.

**Excluded Nodes (specs exist, implementation does not):** !`cat spx/EXCLUDE 2>/dev/null || echo '(no spx/EXCLUDE file found)'`

Git Status: !git status --short || echo 'Not a git repo'

Recent Commits: !git log --oneline -5 || echo 'Not a git repo'

Project Language Indicators: !ls pyproject.toml package.json tsconfig.json 2>/dev/null || echo 'No indication of Python or TypeScript'

Step 0: Check for --agent mode

If $ARGUMENTS contains --agent, extract the node path from the remaining arguments and launch the applier agent:

Agent tool → { "subagent_type": "spec-tree:applier", "prompt": "Apply the spec-tree TDD flow to node: {node-path}" }

The agent runs the full 8-phase flow autonomously and returns when complete. Stop here — do not continue to Step 1.

Step 1: Determine the work queue

If $ARGUMENTS is provided (without --agent): The argument is the node path. The work queue is that single node.

If no argument: Check conversation context for a node the user wants implemented. If nothing is clear, read spx/EXCLUDE. Each non-comment, non-blank line is a node path relative to spx/.

If no work is found, report "Nothing to apply" and stop.

Step 2: Order by dependency

When multiple nodes are queued, sort by numeric index prefix (lower first). Lower-indexed nodes constrain higher-indexed ones and must be applied first.

Step 3: Apply each node

For each node path, in order:

3a. Remove from EXCLUDE

If the node is listed in spx/EXCLUDE, remove its line. Then run the project's sync command (defined in spx/CLAUDE.md) so the node's tests join the quality gate.

3b. Load context

Skill tool → { "skill": "spec-tree:contextualizing", "args": "spx/{node-path}" }

3c. Run the TDD flow

Skill tool → { "skill": "spec-tree:applying" }

This runs the full 8-phase flow: methodology, context, architect, audit, test, audit, implement, audit.

3d. Commit the applied node

Skill tool → { "skill": "spec-tree:committing-changes" }

3e. Move to next node

Do NOT stop or ask the user. Proceed immediately to the next node.

Step 4: On failure

If a node's TDD flow fails (audit gate rejects after max retries, tests won't pass, or implementation blocked):

• STOP the loop — do not skip to the next node
• Report which node failed and at which phase
• Leave remaining nodes in spx/EXCLUDE

Step 5: Report

When all nodes are applied (or on failure), report final status.

<success_criteria>

• All targeted nodes applied (tests passing, implementation complete)
• Each node committed individually
• Applied nodes removed from spx/EXCLUDE
• No nodes skipped — dependency order respected

</success_criteria>