strang

What problem does it solve? When a task touches more than one file or contains independent pieces, editing everything in one pass leads to merge conflicts, lost work, and unverifiable claims. This Skill defines how to split such work into independent strands before the first edit, so each piece has a clear owner and results come back usable. ## Core Features & Use Cases - Split decision rules: Split when a task edits more than one file or has more than two independent pieces; otherwise write one sentence justifying working alone. - File-ownership orders: One file, one owner; foreign files named by absolute path, with the program referenced as the whole videopodcast_magic/ folder so borders survive internal restructuring. - Prepared edits for foreign files: Deliver verbatim old-text/new-text pairs anchored on text (never line numbers), with each anchor counted to match exactly once. - Order template and return contract: A fill-in template covering machine constraints (gtimeout, offscreen windows, no commits, scratch-space rules) plus required returns: counter-proof red lines, measured-or-read statements, and report-don't-repair findings. - Use Case: Before refactoring a Python project across several modules, use this Skill to cut an order per strand naming owned and foreign paths, prepare anchored edits for shared files, and collect counter-proofs when strands report back. ## Quick Start Use the strang skill to cut an order for this task before making any edits, since it touches more than one file.