What problem does it solve? Turning a saved implementation plan into actual work requires manually creating a branch, naming it consistently, and keeping the plan linked to that branch for later reference. This Skill automates that handoff by resolving a saved plan file, creating the target branch, and attaching the plan as a named Markdown key in Branch Memory. ## Core Features & Use Cases - Plan Resolution: Resolves a saved plan file from an absolute or home-relative path before branching. - Branch Creation with Context: Creates the target branch via plain Git or Graphite and attaches the plan as a named Markdown key in Branch Memory. - Slug Derivation: Derives a kebab-case 3-7 word slug from plan content to drive the branch name and attached-plan key. - Use Case: After writing and saving an implementation plan, ask the agent to branch from that plan; it creates the branch, attaches the plan under a slug like add-oauth-login-flow.md, and reports the branch, namespace, key, and commit. ## Quick Start Ask the agent to create an implementation branch from your saved plan file and attach the plan as branch context.
