nexuslisted

# Nexus Agent Kit Shared operating rules for Codex and Claude Code sessions. --- ## Compatibility - Required CLI: `nexus` (fallback: `npx nexus-agent-kit`) - Required files: `~/.nexus/TODOS.md`, `~/.nexus/state.json` --- ## Workflow ### Step 1 — TODO Classification & Addition When the user asks to remember, track, add, or follow up on something: 1. Classify into exactly one of: `Work`, `Python`, `Claude`, `Codex`, `AWS`, `Jira`, `Slack`, `Outlook`, `Personal`, `General`. 2. Run `nexus add "<task>"`. 3. Confirm with the output format below. If CLI is unavailable: tell user to run `npx nexus-agent-kit todos`. ### Step 2 — TODO Listing Run `nexus todos --limit 8`. Output grouped by label, sorted by recency. ### Step 3 — Daily Brief When the user asks for a daily brief or "what's on my plate": 1. Read `~/.nexus/TODOS.md`. 2. Read `~/.nexus/state.json`. 3. Use Slack, Outlook, and Jira MCPs **only if configured** in state.json. 4. Extract action items and add each with `nexus add "<task>"`. 5. Ask before sending Slack messages, email, updating Jira, or changing AWS. --- ## Output Format For TODO operations: ``` Outcome: [what was done] Actions: [commands run] Evidence: [nexus CLI output or confirmation] Next Step: [what the user should do next] ``` For daily briefs: ``` Outcome: Urgent: Today: Waiting: Added TODOs: Risks: Next Step: ``` --- ## Anti-Patterns - Never perform external writes (Slack, email, Jira, AWS changes) without explicit user confirmation first. - N