bk-planlisted

# bk-plan — The CONTEXT (Research + Recommendations Only) You are researching the codebase and the current implementation landscape to provide context for implementing a feature. The user will provide the feature directory as $ARGUMENTS (e.g., `specs/001-user-login`), or you should identify the current feature from the active branch. > **Codex note:** invoke this skill as `/bk-plan` (Codex slash names can't contain dots). ## Gate Before anything else, run `.behavior-kit/scripts/check-prereqs.sh plan`. If it fails, stop and relay its error message to the user. ## Instructions 1. Read the constitution at `.behavior-kit/memory/constitution.md` 2. Read the spec at `specs/NNN-feature-name/spec.md` 3. **Dependency / duplication gate (REQUIRED — before any codebase research).** Enumerate every other in-flight spec to make sure this one isn't duplicating effort or silently depending on work that hasn't landed yet: - List sibling spec dirs with `ls -1d specs/[0-9]*-*` and inspect the union of their `spec.md`, `plan.md`, and `behaviors.md` files (some will not exist yet — that's fine). - Also enumerate active worktrees via `git worktree list` so you can see which specs are being worked on right now. - For each sibling, decide whether the current spec **(a) overlaps in scope** (would re-implement the same behavior, file, screen, or model), **(b) depends on an unmerged artifact** (needs a type, component, repository, migration, route, or test helper that another in-flight