Skill Claude CodeCodex
Use when a BA needs to capture a business need before it's broken into epics/tasks — e.g. "write a BRD for X", "document the requirement for Y", or a new feature request that hasn't been analyzed yet. Precedes nexus-plan-work — a BRD is the "why" a whole epic exists, not any single task's description.
Skill Claude CodeCodex
Use when a BA needs to write User Acceptance Test scenarios before a feature goes to the actual business stakeholder for sign-off — e.g. "write UAT scenarios for X", "what should we check with the client before go-live". Distinct from QA's write-test-case — UAT checks the business need is met, not that the code works…
Skill Claude CodeCodex
Use when writing the actual content of a task's description/acceptance criteria before createtask — e.g. "write the user story for X", "what should the AC be for this task". Content-quality companion to nexus-plan-work, which handles the field-by-field creation process but doesn't tell you how to write good…
Skill Claude CodeCodex
Use when an endpoint/payload changes and another repo or team depends on it — e.g. "document the API for X", "what's the contract for this endpoint", a backend task whose frontend counterpart task exists in the same story. Closes the exact gap nexus-pick-up-task flags — "share the contract via a task comment, not just…
Skill Claude CodeCodex
Use before implementing a task complex enough that the approach itself needs sign-off first — e.g. "write a design doc for X", a task that touches multiple services, changes a data model, or has more than one reasonable implementation approach. Not for routine tasks — most tasks should just go straight to…
Skill Claude CodeCodex
Use when a PM needs to plan what goes into an upcoming sprint — e.g. "plan the next sprint", "what should we commit to for sprint N". Uses real Nexus data (backlog, velocity, member workload) rather than a guess at capacity.
Skill Claude CodeCodex
Use for a periodic (weekly/biweekly) progress update to stakeholders — e.g. "write this week's status report", "summarize progress for the client". Pulls real Nexus data rather than a from-memory summary.
Skill Claude CodeCodex
Use when a test case fails and it's time to report it back — e.g. "file a bug for X", "write up why this test failed". Content-quality companion to nexus-pick-up-task's hand-off step (comment + attach evidence + reassign) — this skill is what actually goes in that comment.
Skill Claude CodeCodex
Use when writing the actual step-by-step test cases for a task, once a test plan (if one exists) has set scope — e.g. "write test cases for X". The day-to-day granular artifact, distinct from write-test-plan (scope/approach) and BA's write-uat-scenario (business-facing sign-off).
Skill Claude CodeCodex
Use when planning test coverage for a feature or release before writing individual test cases — e.g. "write a test plan for X", "what needs testing before this ships". One level above write-test-case — scope and approach, not individual steps.
Skill Claude CodeCodex
Use when stuck on a decision that's genuinely another role's call (pm for priority/scope, ba for requirement/acceptance-criteria) and you're running as your own independent process (Agent App, or any unattended claude -p run) — not a spawned Claude Code subagent, so nexus-consult-teammate's in-session Agent-tool…
Skill Claude CodeCodex
Use when stuck on a decision that's genuinely another role's call (a product/priority tradeoff for pm, a requirement/acceptance-criteria question for ba, a technical-feasibility question for dev, a testability/edge-case question for qa) — get a fast, same-session second opinion from that role instead of stopping to…
Skill Claude CodeCodex
Use when starting, resuming, or checking status of work tracked as a Nexus task/ticket via the nexus-mcp tools — e.g. the user says "start this task", "what am I working on", "pick up where I left off", "let's do ALPHA-42", or opens a repo to begin a coding session. Hand-off protocol between people and repos…
Skill Claude CodeCodex
Use when breaking down a feature into epics/stories/tasks in Nexus via nexus-mcp — e.g. the user (PM/BA/Team Lead) says "create a task for X", "break this feature down", "set up the backend and frontend tasks for Y", or asks to plan work that will later be picked up via nexus-pick-up-task. The authoring counterpart to…