Guides & Customization

Master advanced JARFIS patterns — from linking meetings to work items, to customizing agent roles, managing gates, and recovering from interruptions.

Meeting-to-Work Linkage

JARFIS connects meeting outcomes directly to development workflows. Run a meeting first to produce structured outputs, then link those outputs to a work command so the entire pipeline starts with full context.

Step-by-Step

1. Run the meeting command with a topic:

/jarfis:meeting Define the authentication strategy for the mobile app

This produces summary.md, decisions.md, and meeting-notes.md.

2. Link the meeting output to a work command using the --meeting flag:

/jarfis:work Implement mobile auth with biometric login --meeting auth-strategy-meeting

3. Phase 0 (Pre-flight) automatically loads the meeting context. Agents reference meeting decisions throughout all subsequent phases.

Role Configuration

JARFIS uses the required_roles field in .jarfis-state.json to determine which agent roles are active for a workflow. This controls which phases execute and how parallel work is distributed in Phase 4.

{
  "required_roles": {
    "backend": true,
    "frontend": true,
    "ux": false,
    "devops": false,
    "security": true
  }
}

Continuing a Completed Workflow

Use /jarfis:continue to build on a completed workflow — add tests, fix edge cases, or extend scope without starting from scratch.

/jarfis:continue Add unit tests for the auth module
/jarfis:continue Fix the token refresh edge case --mode fix

You can also specify the workflow to continue with --workflow path to target a specific previous workflow's output.

Project Profiles

Project profiles give JARFIS a complete understanding of your codebase — repo structure, dependencies, build tools, and conventions — so every workflow starts with accurate project context.

Working with Gates

Gates are the primary mechanism for human oversight. Each gate offers specific actions to control workflow direction.

Managing the Learning System

JARFIS operates a two-tier learning system that improves output quality over time through accumulated project knowledge.

Learning Cycle

context.md Example

# Project Context
## Tech Stack
- Frontend: Next.js 15, TypeScript strict, Tailwind CSS 4
- Backend: FastAPI (Python 3.12), PostgreSQL 16, Redis
## Conventions
- API responses follow RFC 9457 Problem Details format
- All database models use UUID primary keys
- Commit format: conventional commits

Use /jarfis:upgrade to curate learning items — keep, edit, or remove entries to maintain quality.

Workflow Recovery After Context Compression

JARFIS persists phase and progress state on disk via .jarfis-state.json. No special resume command is needed — the system automatically detects and resumes interrupted workflows.

Modifying JARFIS Itself

Use /jarfis:implement when you want to modify or extend JARFIS itself — add new commands, change agent behavior, or update the pipeline structure.

/jarfis:implement Add a /jarfis:standup command for daily status reports

Practical Examples

Real-world usage patterns for common development scenarios:

Next Steps

• API Reference — Complete command and configuration reference
• Architecture & Concepts — Deep dive into the orchestration model
• Quick Start — Installation and first workflow