Planning Pr

Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.

hashintel Updated 1.7k repo stars

File contents

hashintel/brunch commit fb98d1b870

Frequently asked questions

npx get-skill add hashintel/planning-pr