grimoire-apply

Automating BDD task execution without context loss requires spawning a fresh subagent per task section. This enforces strict session-per-task discipline, tracks progress in tasks.md, and prevents context drift across planned grimoire changes.

A red-green BDD workflow for task management applies planned changes section by section using fresh context. It enforces per-task attempts, produces session handoff notes, and ensures each section is complete before moving to the next.

To execute tasks defined in a markdown file sequentially, target the change tasks directory and process sections one by one. The workflow spawns fresh subagents, tracks progress in tasks.md, and ensures completion before moving to the next section.

Yes, a session-per-task protocol prevents context switching during automated code changes by enforcing fresh context per task. It produces handoff notes for continuity and maintains high-quality execution across task sections.

Limitations of enforcing strict BDD workflows include requiring pre-planned task definitions in a specific directory structure. The workflow cannot execute without a tasks.md file and mandates completion of each section before advancing.

Yes, you can manage task handoff notes for planned changes by enforcing per-task attempts. The workflow produces session handoff notes for continuity, tracks progress in tasks.md, and maintains traceability across sections.