Once ARIA is installed and the MCP server is configured, set up your project.
Step 1: Run /aria-setup
This interactive workflow auto-discovers your workspace and configures ARIA. It asks 3-4 essential questions:
- Platform -- Plane or Linear (auto-detected from available MCP servers)
- Project name -- what is your project called?
- Team/Project -- auto-discovered from the platform, you confirm
- Skill level -- beginner, intermediate, or expert (controls autonomy level)
- Git integration -- enable or disable
Everything else is auto-derived:
- Team ID, workflow statuses, and labels/properties are discovered from the platform
- User name is detected from git config or platform profile
- Autonomy level is derived from your skill level (beginner → interactive, intermediate → balanced, expert → yolo)
- A workspace project is created for early-phase documents
Configuration is saved to _aria/core/module.yaml.
Step 2: Run /aria-git (Optional)
If you enabled git integration, this workflow configures:
- GitHub remote detection or setup
- Default branch detection
- Branch naming convention (e.g.,
TEAM-42/add-auth) - Commit message format (e.g.,
feat(TEAM-42): implement auth) - PR behavior (auto-create, draft mode, auto-push, auto-approve, auto-merge)
Step 3: Run /aria-help
Get context-aware guidance on what to do next. ARIA inspects your workspace and recommends the appropriate workflow based on your project's current state.
Fresh Project?
For a brand new project, the typical starting sequence is:
/aria-brainstorm-- generate ideas/aria-brief-- formalize into a product brief/aria-prd-- create a product requirements document/aria-arch-- define architecture/aria-epics-- break down into epics and stories/aria-sprint-- plan your first sprint