What problem does it solve? When a plan was captured earlier for a branch, context is lost between sessions and agents re-derive decisions or drift from agreed scope. This Skill reloads the attached branch-context plan and implements from it as the authoritative source, with explicit STOP conditions when reality diverges from the plan. ## Core Features & Use Cases - Plan Loading: Runs ns branch-context exec load to fetch the attached plan from Branch Memory, with automatic key selection when exactly one entry exists and fallback to saved session plans or the local plan store. - Contract Enforcement: Applies the branch-context plan contract protocol, comparing current-state excerpts, scope boundaries, and verification gates against live repo state before executing, and stopping on mismatches. - Deviation Discipline: Documents minimal adaptations, treats plan-ruled-out options as open questions when expanding scope, and reports validation results, deviations, and unresolved follow-ups. - Use Case: After a teammate attaches an implementation plan to a feature branch, you check out the branch and ask the agent to implement from the branch context; it loads the plan, verifies anchors, implements step by step, and reports any STOP conditions instead of guessing. ## Quick Start Ask the agent to implement the attached branch-context plan on the current branch and follow its scope and verification gates.
