Skill Claude CodeCodex
Add a new code session to an existing BMad project hub. Generates the session file, updates the hub CLAUDE.md session map, and creates a sibling repo directory with CLAUDE.md ready for git. Use when the user says "add session", "add repo", "add backend", "add iOS", or similar.
Skill Claude CodeCodex
Scaffold a new BMad project hub interactively. Asks for project name, architecture preset, and repo names — then generates all session files, hub CLAUDE.md, and per-repo CLAUDE.md files. Adapts to the environment: direct file generation in Claude Code, guided text output elsewhere. Use when the user says "setup hub"…
Skill Claude CodeCodex
Mark the current story complete. Updates epic frontmatter, session file, adds QA ready-to-test entry, commits hub changes, and pushes. No user input required. Use when a story is fully implemented and passing lint/tests.
Skill Claude CodeCodex
Check for new PM decisions, answers, and sprint changes relevant to this session. Reads the planning session and own session file. No user input required. Use at the start of each dev session or when the user says "check PM updates", "any PM changes", "what did PM decide".
Skill Claude CodeCodex
Add a completed story to QA's ready-to-test queue. Updates qa-session.md with what to verify, commits, and pushes. No user input required. Use after a story is merged and deployed, or when the user says "notify QA", "ready for QA", "tell QA story X is done".
Skill Claude CodeCodex
Start the next story from this session's sprint queue. Reads the session file, identifies the top priority story, loads the spec from the hub epics, and begins implementation via /bmad-dev-story. No user input required. Use when the user says "start next story", "pick up next", or "what's next".
Skill Claude CodeCodex
Lock a design or product decision. Records in the planning session decisions log, saves to persistent memory if available, and commits. Use when the user says "lock this", "that's decided", "record this decision", or makes a definitive product/design choice.
Skill Claude CodeCodex
Cross-session PM status check. Reads all session files and produces a single status table showing current sprint, active stories, blockers, and open PM actions. Use at the start of every PM session or when asked "what's the status", "check sessions", or "what's going on".
Skill Claude CodeCodex
File a new story in an existing epic. Updates the epic frontmatter (total count, story entry), appends the story spec with Given/When/Then ACs, and commits to the planning repo. Use when the user says "file a story", "add a story", "create story X.Y", or describes a feature that needs a story.
Skill Claude CodeCodex
Sync session files after a story ships or priorities change. Updates the relevant session's sprint queue, marks completed work, adjusts ordering, and commits. Use when the user says "story X is done", "update the sessions", "mark X complete", or after a sprint wraps.
Skill Claude CodeCodex
Answer open questions from session files and record the PM's response. Use when the user says "answer the question from X session", "triage the questions", or when a session's ❓ Questions for PM section has open items.
Skill Claude CodeCodex
File a bug found during testing. Creates a properly formatted bug entry in the backlog with the correct bug-NNN ID, steps to reproduce, expected vs actual, and AC reference. No user input required beyond the bug description. Use when the user says "file a bug", "log this bug", or a test case fails.
Skill Claude CodeCodex
Mark a story as failed QA. Updates qa-session.md to show the failure, references the bug filed, and flags the owning dev session to investigate. No user input required. Use after /qa-bug when a story cannot be verified due to a bug.
Skill Claude CodeCodex
Mark a story's test cases as verified and passed. Updates qa-session.md, commits, and pushes. No user input required. Use after all test cases for a story have passed.
Skill Claude CodeCodex
Pick up the next story from the QA ready-to-test queue. Reads qa-session.md, loads the test file and story ACs, and begins verification against production URLs. No user input required. Use when the user says "start QA", "test next story", or "what's ready to test".