⚡ signal-state

This skill manages the Continuous State Engine for the SIGNAL protocol. It transitions the context window from an ephemeral chat history to a persistent .signal_state.md file on disk.

When to use

• Start of session: Read .signal_state.md if it exists. It IS your context.
• Significant actions: Update state on sub-task completion, PR merge, or focus shift.
• Trigger: /signal-state → refresh file immediately.

How it works

Use write_file or replace to modify .signal_state.md in project root. No scripts required.

Format (.signal_state.md)

YAML frontmatter + 3 blocks: Context, Progress, Next.