branch-context-from-plan

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# branch-context-from-plan

Resolve a saved plan, create the target branch, and attach a named Markdown plan key as branch context in Branch Memory. Part of the branch-context family — load the `branch-context` umbrella for the shared lifecycle, storage, and safety model.

## Commands

Resolve the saved plan when needed:

```bash
enriched-plan exec resolve [absolute-or-home-plan-file.md] --format json
```

Create and attach:

```bash
ns branch-context exec from-plan \
  --slug <branch-context-slug> \
  --plan-file <absolute-or-home-plan-file.md> \
  [--branch <target-branch>] \
  [--branch-creation plain-git|graphite] \
  [--summary "<one sentence>"] \
  --format json
```

## Workflow

1. Resolve the saved plan first if a path is given or none is known.

2. Derive `<branch-context-slug>` from plan content: kebab-case, 3-7 specific words, no dates/random IDs/generic-only names. This drives the default target branch and the attached-plan key `<branch-context-slug>.md`.
3. Choose the branch creation method before invoking `ns branch-context exec from-plan`. In this repo, include `--branch-creation graphite` unless the user explicitly requested plain Git. For precedence and Graphite method details, see the `branch-context` umbrella's `references/lifecycle.md` (`## Branch creation policy`).
4. Pass `--branch` only when the user requested a specific target branch.
5. Parse the standard Clinkr JSON envelope and report `data.branch`, `data.branchCreation`, `data.namespace`, `data.key`, `data.refName`, `data.commit`, `data.sourceFile`, and `data.slug`.

## Recovery

- No saved plan: run the write-plan workflow first, or provide an absolute/home-relative `.md` path.
- Slug rejected: derive a clearer 3-7 word slug and retry once before asking.
- Target branch exists: stop; ask whether to choose another `--branch` or inspect the existing branch.
- Branch Memory entry exists: do not overwrite; report namespace/key and ask.
- Graphite setup fails after branch creation: report the partial branch state; do not attach a plan manually unless the user explicitly directs recovery.

From nseng-ai/ns, MIT.

More from nseng-ai/ns