wise-forklisted

# /wise-fork - reorient a forked session Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. ## Why this skill exists Forking a session copies the whole conversation into a new, parallel session. The copy inherits every open thread: half-finished tasks, promised next steps, an in-progress plan. Left alone, the agent in the fork will try to finish them - duplicating work the original session is still doing, and possibly fighting it over the same working tree. This skill draws a hard line: context before the fork is background, work before the fork is not yours. ## Invocation ``` /wise-fork /wise-fork <new goal in free prose> /wise:wise-fork [<new goal>] # canonical namespaced form ``` ## Arguments Read `$ARGUMENTS`. Everything (if anything) is free-form text: the first task of this forked session. No flags, no validation - prose is prose. When empty, acknowledge the fork and wait for the user's next message. ## Procedure ### 1. Adopt the fork contract From this point on, apply these rules to the entire conversation above this invocation: - **Context is background, not a backlog.** Facts, decisions, codebase knowledge, and user preferences learned before the fork stay valid - use them freely as reference. - **In-flight work belon