knot0-com

This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.

Use instead of chaining 3+ Bash calls, grep/cat/find pipelines, or any multi-step data processing. This skill should be used when the user asks to "start a scratchpad", "use the REPL", "scratchpad mode", "persistent Python session", or when a task involves exploration, analysis, or file processing that would benefit from composing operations in code rather than making individual tool calls. It creates a persistent Python REPL via tmux where variables survive across turns and only print() output enters context — a context-efficient alternative to Bash for data-heavy work.

Use for code verification, debugging, and deep code analysis without running tests. This skill should be used when the user asks to "verify my changes", "check my patch", "find the bug", "why does this test fail", "are these changes correct", "review this diff", or when analyzing code semantics that require tracing execution paths. It applies semi-formal structured reasoning from the Agentic Code Reasoning paper (Ugare & Chandra, Meta, 2026) to prevent unsupported claims and force evidence-based analysis.