Inconsistent behaviour with "files_to_modify" from roadmap.json

[ivankg]

Steps to Reproduce:

1. Create a roadmap.json with a step that includes files_to_modify, e.g. step 01-01 listing specific adapter/use-case files
2. Run /nw:execute @nw-software-crafter "app_name" "01-01"
3. Observe the agent's behavior — it does not create or modify the files listed in files_to_modify
4. The agent creates whatever files TDD demands, with no awareness of the planned file list

Expected Behavior: The software crafter should receive the files_to_modify list and use it as both implementation guidance (which files to create/modify) and a boundary constraint (don't touch files outside this list).

Root Cause Analysis:

The disconnect is in /nw:execute command (commands/execute.md):

1. TASK_CONTEXT template (line 67) extracts these fields from the roadmap step:

   name|description|acceptance_criteria|test_file|scenario_name|quality_gates|
   implementation_notes|dependencies|estimated_hours|deliverables
   

   files_to_modify is NOT in this list — it's never extracted or passed to the agent.

2. BOUNDARY_RULES (line 142) says:

   - Only modify files listed in step's files_to_modify
   

   This rule references files_to_modify, but the agent never receives this data in its prompt context.

3. Result: The agent gets a boundary rule it cannot enforce because the data it references was never provided. The agent proceeds with pure TDD, creating files organically based on test demands.

Suggested Fix:

Add files_to_modify to the TASK_CONTEXT extraction list in commands/execute.md, line 67:

[11PJ11]

Thank you @IlTorre for the detailed root cause analysis — it was exactly right.

Fixed in v3.0.0 (currently RC, releasing soon).

files_to_modify was missing from the TASK_CONTEXT extraction list in execute.md while being referenced in BOUNDARY_RULES — exactly as you described.

Fix: Added files_to_modify to the TASK_CONTEXT field extraction in both:

• /nw-execute (the skill that dispatches steps)
• /nw-deliver (the orchestrator that builds the DES template)

The crafter now receives the planned file list and can use it as both implementation guidance and a boundary constraint.

To upgrade when released: pipx upgrade nwave-ai && nwave-ai install

---

This response was generated with Claude Code on behalf of the nWave team.