raise

Interactive adapter setup for Jira and Confluence. Detects available backends, discovers projects/spaces, generates validated YAML config. 3-4 questions max.

Evaluate design proportionality using Beck's four rules. Use after implementation.

Root cause analysis using the method best suited to the bug. Phase 3 of bugfix pipeline.

Push branch, create MR, verify artifacts complete. Phase 7 of bugfix pipeline.

Execute fix tasks with TDD and all validation gates. Phase 5 of bugfix pipeline.

Decompose fix into atomic TDD tasks. Phase 4 of bugfix pipeline.

Retrospective, pattern extraction, and process improvement. Phase 6 of bugfix pipeline.

Run the full 7-phase bugfix pipeline with 3 HITL gates. Use to orchestrate a bug fix.

Initialize bug branch, reproduce, and create scope artifact. Phase 1 of bugfix pipeline.

Classify bug in 4 dimensions and set Jira custom fields. Phase 2 of bugfix pipeline.

Find root cause using 5 Whys, Ishikawa, Gemba. Use when encountering errors or defects.

Scan codebase, extract symbols, and build knowledge graph. Use for codebase discovery.

Sync module docs with knowledge graph. Use when architecture docs drift.

Run self-diagnostics and guide fixes. Use to troubleshoot RaiSE issues.

Close epic with retrospective, push, and merge request. Use after all stories done.

Design epic scope, stories, and architecture. Use for work spanning 3-10 features.

Generate architecture docs and publish to Confluence. Use before epic close.

Sequence epic stories into milestones and dependencies. Use after epic design.

Run the full epic lifecycle with delegation gates. Use to orchestrate an epic.

Initialize epic directory, brief, and tracker entry. Use to begin a new epic.

Register an MCP server conversationally. Use to add a new MCP integration.

Remove an MCP server with dependency checking. Use to unregister a server.

Check health of registered MCP servers. Use to diagnose MCP connectivity.

Shape a vague idea into a problem brief. Use before epic design for new initiatives.

Set up governance for a new project. Use after rai init on a greenfield project.

Discover conventions and set up governance. Use after rai init --detect on existing code.

Audit code for semantic bugs, type lies, and test muda. Use after implementation.

Research with triangulated evidence to inform decisions. Use before ADRs or evaluations.

Capture session outcomes and update memory. Use to close a working session.

Write a narrative session diary entry to Confluence. Use before session close.

Load context and propose session focus. Use at the start of every working session.

Merge story branch to dev and update tracking. Use after story review.

Create lean story spec for human review and AI alignment. Use before story plan.

Execute plan tasks with TDD and validation gates. Use after story plan.

Decompose story into atomic tasks with TDD verification. Use after story design.

Extract learnings and persist patterns from completed story. Use after implementation.

Run the full story lifecycle with delegation gates. Use to orchestrate a story.

Create story branch and scope commit. Use to begin story work.

Onboard a developer to RaiSE interactively. Use for first-time setup.