What problem does it solve? In the mismAgent architecture-driven flow, research unknowns and deprecated cross-deploy endpoint removals still need to be tracked as files, but they are not building blocks. This Skill writes those two node kinds with the correct templates, folder-based state, and closure rules so nothing falls through the cracks. ## Core Features & Use Cases - Spike nodes: Creates type: spike files capturing a research question, its closure criterion, and the blocks it unblocks, with a defined closure protocol (ADR or AC resolution, moved to done/, never deleted). - Cleanup nodes: Creates type: cleanup files for removing a deprecated cross-deploy operationId after consumers migrate, gated by a verifiable ready_when condition instead of a task dependency. - Folder-as-state: Writes nodes to <output_dir>/features/<feature>/tasks/<side>/<state>/<slug>.md where the folder itself encodes state, with no status: field. - Use Case: During the model movement, the tactical-modeler materializes a context-map spike asking whether OCR state is persisted on the aggregate; this Skill emits the spike node file that blocks downstream blocks until resolved. ## Quick Start Ask the agent to write a spike node for the open question about OCR state persistence in the current feature's backlog.
