write-task

What problem does it solve? In the mismAgent architecture-driven flow, most work items are blocks, but two node kinds still need to exist as files: research spikes (unknowns that block consumers) and cleanup nodes (removal of deprecated cross-deploy operationIds). This Skill writes those node files with the correct frontmatter, folder-based state, and closure or readiness protocols. ## Core Features & Use Cases - Spike node generation: Creates type: spike files capturing the question to answer, the closure criterion, and which blocks the spike unblocks, with a defined closure protocol (ADR for mechanizable decisions, ACs/tests_nl for discursive ones). - Cleanup node generation: Creates type: cleanup files for removing deprecated cross-deploy operationIds, gated by a verifiable ready_when condition such as zero consumer references. - Folder-as-state convention: Writes nodes to tasks/<side>/<state>/<slug>.md where the folder itself encodes state, keeping spikes and cleanup nodes separate from the blocks tree. - 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 the dependent blocks until closed. ## Quick Start Ask the agent to write a spike node for the open question about OCR state persistence in the current feature's backlog.