Way of Teams is the AI engineering harness for modern teams. It combines tickets, standups, skills tracking, AI agents, and observability in one real-time workspace.

Prerequisites

• Elixir 1.18+
• PostgreSQL 16+
• Node.js 20+ (for assets)

Getting Started

1. Sign Up — Create your account in one click with GitHub, Google, or Apple
2. Join a Meeting — Start video calls directly in Way of Teams
3. Let AI Listen — Our AI captures decisions, tasks, and priorities from your conversations
4. Watch It Build — After the meeting, AI agents create tickets, plans, and implement features automatically

AI Engineering Harness — Free on Every Plan

Once you're signed up, the AI Engineering Harness is ready to use. It includes:

• 53 Battle-Tested Skills — Auto-ticket creation, backlog grooming, GitHub automation, PR reviews, postmortems, runbooks, and more
• 12 Specialist Agents — Codebase analyzer, locator, pattern finder, thoughts analyzer, web researcher, coder, planner, reviewer, scout, and more
• 5 Unified Commands — /create-plan, /implement-plan, /validate-plan, /commit, /debug — consistent workflow across all platforms

Works identically across OpenCode, Claude Code, Codex, Antigravity, Pi, and Wo Code — one harness, every tool.

Way of Teams is built on the Ash Framework with:

• Phoenix LiveView for real-time UI
• AshPostgres for data persistence
• AshJsonApi for REST APIs
• AshGraphql for GraphQL APIs
• OpenTelemetry for observability
• Jido for AI agent orchestration

Core Domains

• Accounts — Developer management
• Tickets — Issue tracking with status workflow
• Skills — AI tool skill management
• Standups — Daily standup tracking
• Notifications — System notifications
• Insights — Skill reports and analytics
• Kanban — Visual project management
• Frrd — Change tracking for f-rr-d

AI Engineering Harness

Explore the full catalog of skills, agents, and commands:

• AI Harness Repository
• f-rr-d Thoughts Repository

Community & Support

• GitHub Issues for bug reports and feature requests
• GitHub Discussions for questions and ideas
• Enterprise support available on Team and Enterprise plans

                            ┌─────────────────────────────────────────────────────────────┐
                            │                  YOUR WAY-OF JOURNEY                        │
                            │                                                             │
                            │  1. What do you want to do?                                │
                            │  2. What do you want to name it?                           │
                            │  3. Let's install our system.                               │
                            │  4. Let's make two repos based on the name.                │
                            │  5. Let's make your first ticket.                           │
                            │  6. Let's implement your first ticket.                      │
                            │  7. Look at what you just did.                              │
                            │  8. Let's create your next tickets.                         │
                            │                                                             │
                            │              ──→ You're building now.                       │
                            └─────────────────────────────────────────────────────────────┘
              

Step 1 — What Do You Want To Do?

Every project starts with a question: "What problem are you trying to solve?"

• Problem statement (even a rough one)
• Who it's for
• What success looks like

We capture it as a structured ticket, break it into actionable pieces, and prioritize by impact.

Step 2 — Name Your Project

Your project gets a unique identity that defines your team's workspace.

• Project Name — e.g., "teams" becomes your Way of Teams instance
• Ticket Namespace — All tickets follow the format: WOTEAMS-XXX

Step 3 — Harness is Ready

The AI Engineering Harness activates automatically once you're signed up. No installation needed!

Step 4 — Harness Activates

The AI Engineering Harness is now active with:

• 53 Skills — Auto-ticket creation, backlog grooming, GitHub automation, PR reviews, postmortems, runbooks
• 12 Specialist Agents — Codebase analyzer, locator, pattern finder, thoughts analyzer, web researcher, coder, planner, reviewer, scout
• 5 Unified Commands — /create-plan, /implement-plan, /validate-plan, /commit, /debug

Step 5 — Create Your First Ticket

Your ticket follows a standardized format that AI agents can process:

• Problem Statement — What problem are you solving?
• Desired Outcome — What does success look like?
• Acceptance Criteria — How do we know it's done?

Step 6 — AI Agents Build It

• /create-plan — Turn your ticket into a step-by-step implementation plan
• /validate-plan — Check feasibility, dependencies, and risks before building
• /implement-plan — Execute each phase with automated testing and commits
• /commit — Well-structured git commits ready for review

Agents: Planner → Coder → Reviewer → Debugger

Step 7 — See It Working

Your feature is live on your team's dashboard. The ticket status updates to "Done" automatically. Git history shows exactly what was built and when.

Step 8 — Keep Building

The flywheel spins: Tickets → Harness → Working Software → Learning → More Tickets

Problem	Solution
"I don't know where to start"	Step-by-step journey with guided onboarding
"I can't manage all this complexity"	AI Engineering Harness handles the tooling
"I lose track of what I was doing"	thoughts/ context engine remembers everything
"I don't know how to use AI tools properly"	53 pre-built skills and 12 specialized agents
"My work doesn't feel organized"	Standardized ticket format, namespace conventions, unified dashboard
"I can't see what my team is doing"	Dashboard with activity metrics, review queues, standups, real-time notifications

Dark-themed, single-page-app style, everything one click away. Sidebar with 18 links, sticky header with org switcher, real-time notifications, embedded AI chat panel.

Sidebar Navigation

                            ☰  Dashboard        📋  Standups
                            🎫  Tickets          🤖  AI Chat
                            📋  Kanban           💬  Team Chat
                            📊  Skills           💡  Ideas
                            ✅  Review Queue     📰  News
                            👥  Developers       🔧  Admin
                            ⚙  Settings         👤  My View
                            📄  Docs             🔗  F-rr-d Changes
              

• Dashboard — Command center with stats, tickets, standups, AI chat
• Tickets — Full management with filters, search, bulk ops, activity timeline
• Kanban — Board/List/Calendar views, drag-and-drop, real-time sync
• Standups — Daily check-in with history and focus scores
• AI Chat — Streaming, thinking blocks, per-session settings, 30+ providers
• Team Chat — Real-time messaging, video calls, AI meeting notes → tickets/kanban/plans
• Ideas — Submit, vote, prioritize, discuss, status workflow
• News — Announcements with read tracking
• Review Queue — Lead-only view with Approve/Request Changes/Reject
• My View — Personal dashboard with stats and quick actions
• Admin — Team management, activity dashboard, Jido Studio, f-rr-d sync

You sign up. You talk. It builds.

1. Sign Up — One click, GitHub/Google/Apple
2. Join the Meeting — Video call in Way of Teams
3. Way of Teams Listens — AI absorbs: decisions, tasks, dependencies, priorities
4. After the Meeting — AI goes to work
5. You Come Back To — Kanban board, Tickets, Plan, Assignments, Standup summary
6. You Review. You Adjust. You Go.

Time	What Happens
0-5 min	Tell us what you want to build
5-10 min	Create your repos and name your project
10-15 min	Install the harness and configure your tool
15-20 min	Write your first ticket together
20-25 min	AI agents plan and implement your first feature
25-30 min	You see it working. You're a builder now.

Tool	Config Dir	Naming	Type
OpenCode	~/.config/opencode	kebab-case	Lightweight TUI (MCP + LSP)
Claude Code	~/.claude	snake_case	Unified Skills system
Pi	~/.pi/agent	kebab-case	Programmable Integration (TS/JS)
Wo Code	~/.wocode	kebab-case	CLI Coding Agent
Antigravity	~/.antigravity	snake_case	System Integration with sidecars
Codex CLI	~/.codex	snake_case	OpenAI's Codex CLI

Core Journey Skills

Skill	When You Use It	What It Does
ticket-manager	"I need to create/organize tickets"	Creates, updates, manages tickets with proper naming
create-plan	"I have a ticket, now what?"	Turns ticket into step-by-step implementation plan
validate-plan	"Is this plan solid?"	Validates plan before implementation
implement-plan	"Let's build this"	Executes plan phase by phase, committing after each
commit	"Save this work"	Creates well-structured git commits
standup	"What did I do today?"	Generates daily standup from git and ticket history

GitHub Automation Skills

Skill	What It Does
github-branch	Creates feature branches from tickets
github-pr	Creates PRs linked to tickets
github-review	Reviews PRs with structured feedback
github-sync	Keeps branch up-to-date with main
github-release	Tags and releases with changelog
github-issue	Bi-directional sync with f-rr-d tickets

Research & Analysis Skills

• research-codebase — Deep-dives into codebase
• improve-codebase-architecture — Finds friction, proposes refactors
• self-documentation — Answers "How do I...?" from project docs
• knowledge — Stores and retrieves learned knowledge

Documentation Skills

• postmortem-manager — Generates incident postmortems
• runbook-manager — Creates production runbooks
• session-export — Captures working session history
• document-generation — Generates offers, invoices, reports
• write-a-prd — Turns idea into structured PRD
• prd-to-issues — Breaks PRD into vertical-slice issues

Workflow Skills

• init-harness — Initializes harness in repository
• agents-md-manager — Keeps AGENTS.md files accurate
• ticket-organization — Audits, archives, organizes tickets
• fixes-manager — Cross-project fix/release notes
• rules-manager — Manages coding rules
• usage-rules — Syncs LLM rules from Elixir deps
• validate-podman — Validates Podman/Quadlet configs
• alliner-compliance-check — Deep f-rr-d compliance validation

Build Skills

• build-tool — Universal builder
• build-tool-skill/agent/cli/config/extension/keybindings/prompts/themes/tui

Specialized Skills

• tdd — Test-driven development
• debug — Debug issues
• git-commit-helper — Well-structured commits
• help-command — Unified help system
• sales — Sales knowledge
• auto-ticket-creator — Monitors codebase, auto-creates tickets
• backlog-groomer — Ideas into structured tickets

Agent	What It's Good At
codebase_investigator	Deep-dives into implementation, traces data flow
codebase_locator	Finds specific files, functions, components fast
codebase_pattern_finder	Finds similar implementations and patterns
thoughts_analyzer	Parses research docs for insights
thoughts_locator	Finds relevant docs in thoughts/
web_search_researcher	Researches external sources
coder	Implements code — turns plans into production-ready code
planner	Designs implementation plans
reviewer	Reviews code quality, writes audit reports
scout	Quick recon — finds files, answers code questions
netlify_troubleshooter	CI/CD diagnostics, build pipeline issues
README	Generates and maintains README documentation

Command	What Happens
/ticket-create	Interactive wizard: problem → outcome → scope → creates ticket
/create-plan	Reads ticket, analyzes codebase, generates phased plan
/validate-plan	Checks feasibility, dependencies, risks before implementing
/implement-plan	Executes each phase: changes, tests, commits per phase
/commit	Analyzes changes, drafts message, stages and commits

Other Useful Commands

• /standup — Scans git + tickets → structured standup
• /debug — Reads logs, examines state, proposes fix
• /help — Shows all skills, commands, agents (searchable)

Everything persists in the thoughts/ directory. This is your project's memory.

                            thoughts/
                            ├── global/                    # Cross-project concerns
                            ├── shared/
                            │   ├── tickets/              # All tickets (WOTEAMS-001-*.md)
                            │   ├── plans/                # Implementation plans
                            │   └── research/             # Notes, stack traces, code flows
                            └── <project>/
                                ├── docs/                 # Architecture, decisions, guides
                                ├── shared/               # Project-specific tickets, plans
                                └── <developer>/          # Personal workspace