dnd-simulator

Update living documentation to match current codebase state. Two modes: `/update-docs` — incremental, checks git log since last run; `/update-docs full` — deep-reads actual code and compares with all docs. Use when user says "update docs", "docs are stale", "sync documentation", or after a batch of changes lands.

Advance the dnd-simulator sprint pipeline by reading repository state, selecting the next project playbook, and executing exactly one pipeline step. Use when the user invokes /go or $go, or says go, next, continue, дальше, продолжай, or asks Codex to keep the current dnd-simulator sprint moving.

Close the current sprint: verify all phases done, audit completed, post-audit E2E green, integration tests green, then update docs, commit, push, and wait for CI. Blocks if anything is off. Use when user says "close sprint", "finish sprint", "sprint done", "wrap up sprint", or when all phases are complete and it's time to finalize.

Determine the next step in the sprint pipeline and execute it. Reads docs/STATUS.md, analyzes current state, and calls the appropriate skill. Use when user says "go", "next", "continue", "what's next", "продолжай", "дальше", or just wants to keep the pipeline moving without thinking about which skill to invoke.

Run E2E regression tests via Playwright against the live app. Follows the playbook in docs/e2e-playbook.md plus auto-discovered scenarios from recent changes. Writes a report to docs/e2e-reports/. Use when user says "e2e", "run e2e", "regression", "test everything", "full test", "smoke test", or wants to validate the app works end-to-end. By default skips LLM scenarios; pass --with-llm to include them. Can also be invoked by other skills (close-phase, close-sprint) as part of their workflow.

Implement the next pending task in the current sprint phase. Follows TDD: write tests first (RED), then implement (GREEN), verify all tests pass, update docs, commit. Use when user says "implement", "next task", "work on task", "start task", "do the task", or when the user wants to pick up the next piece of work in an active sprint. Also trigger when user says "implement task N" to target a specific task.

Plan a new sprint: choose scope from backlog/roadmap, break into vertical phases, create sprint docs. Use when user says "new sprint", "next sprint", "plan sprint", "start sprint", "sprint planning", or after a sprint is completed and it's time to pick up the next chunk of work. Also trigger when user asks "what should we work on next" or "what's the priority now" in the context of this project.

Fully autonomous sprint orchestrator — an experimental hands-free development format with NO human in the loop. Runs the full sprint pipeline by spawning one fresh agent per pipeline step; each agent does exactly one granule (/plan-phase, /implement one task, /close-phase, /audit, etc.) and exits. The orchestrator is the SOLE decision authority: it makes every call itself, answers any clarifying questions its sub-agents raise, and ends the run only on success or an unrecoverable dead-end — never to ask a human. Optionally bounded: `/meta-go N` runs at most N granules then stops with a resume report. Use when the user says "meta-go", "run the sprint", "autopilot", "автопилот", "прогони спринт", or wants to leave and come back to a finished sprint.

Analyze audit findings in context of the current sprint. Triages into three buckets: quick-fixes (do now), sprint-relevant (refactor fuel), and backlog (defer). Does NOT auto-fix or update files — presents findings and waits for user decision. Use when user says "triage", "audit triage", "review audit", "what should we fix", "prioritize findings", or after /audit completes and the user wants to decide what to act on. Also useful between phases to decide if a refactor phase is needed.

Close the current sprint phase: run integration tests (add new ones if needed), run E2E via the /e2e skill, and mark the phase complete if no blockers. Use when user says "close phase", "finish phase", "phase done", "e2e", "run e2e", "test the phase", "verify phase", or when all tasks in a phase are marked done and it's time to validate before moving on.

Generate tasks for the current sprint phase. Reads docs/STATUS.md, reviews code, breaks the phase into testable tasks with TDD approach (tests first, then implementation). Use when user says "plan phase", "generate tasks", "break down phase", "what are the tasks", "task generation", or when a new phase is ready to start after the previous one was completed. Also trigger when user asks "what's next" and there's an active sprint with an unplanned phase.

Scan the dnd_simulator codebase for dead code, code smells, security issues, architecture violations, and test gaps. Creates/updates docs/audit.md with actionable findings. Use when user says "audit", "scan", "check code quality", "check architecture", or wants to find layer dependency violations, impure rules, missing tests, or drift from design principles in CLAUDE.md.