Menu
Keep prompt template behavior consistent across CLI and cron by reusing one resolver pipeline.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Prevent gateway projects from taking compile-time dependencies on extension assemblies.
Standard collaboration protocol for all squad agents
Prevent refresh regressions by paging conversation history from newest entries
Fast session investigation using BotNexus Probe CLI (preferred) or Python helper scripts. Use when debugging session state, resuming issues, message routing, checking what sessions exist for an agent, reviewing gateway logs for errors, or correlating events across logs/sessions/traces.
Use when creating GitHub issues, opening worktrees, naming branches, or managing the full lifecycle of a work item on sytone/botnexus. Enforces consistent issue titles, label application, worktree creation, branch naming, PR linking, and cleanup. Triggers on: "create an issue", "open a worktree", "start work on", "file a bug", "add an issue for", "new feature issue", "track this as an issue".
Design spec lifecycle management — creating, reviewing, transitioning, and archiving specs in docs/planning/
| name | prompt-template-resolver-parity |
| description | Keep prompt template behavior consistent across CLI and cron by reusing one resolver pipeline. |
| domain | platform-cli |
| confidence | high |
| source | earned |
Use this when adding or changing prompt-template behavior in CLI, cron, or chat-triggered flows.
.prompt.md and .prompt.json; when both formats exist for the same template name, prefer .prompt.md..prompt.md front matter with bounded keys (name, defaults, parameters) and preserve markdown body line breaks for rendering.