# IDEA-019: iEvo Apps — Vertical AI Workflow Bundles

**Date:** 2026-03-04
**Source:** user
**Status:** raw

## Idea

Introduce a higher-level distribution unit above individual agents: an **iEvo App**. An app bundles everything needed to solve a specific end-to-end use case — agents, pipelines, and MCP servers — into a single installable package. The user installs one app and gets a complete working system, no manual wiring.

```
ievo install github-pr-reviewer
→ agents deployed to .claude/agents/
→ pipeline deployed to .ievo/pipelines/
→ MCP server configured in .mcp.json
→ works immediately
```

## App Structure

```
my-app/
├── app.yaml              # manifest: name, version, description, author, deps
├── agents/               # agent .md files (UAF format)
│   ├── analyzer.md
│   └── reviewer.md
├── pipelines/            # deterministic workflow YAML files
│   └── main.yaml
├── mcp/                  # MCP server configs or embedded servers
│   └── github.json
├── skills/               # optional skills
│   └── post-comment.md
└── README.md
```

## app.yaml Example

```yaml
name: github-pr-reviewer
version: 1.2.0
description: Automated PR review pipeline with code analysis and inline comments
author: ievo-community
license: MIT

agents:
  - pr-analyzer      # uses claude (powerful tier)
  - code-reviewer    # uses claude (standard tier)
  - comment-writer   # uses ollama (fast tier — saves tokens)

pipelines:
  - pr-review        # entry pipeline, triggered by GitHub webhook

mcp:
  - github           # GitHub API — issues, PRs, comments
  - filesystem       # repo file access

requires:
  credentials:
    - GITHUB_PAT_TOKEN
  ievo: ">=0.5.0"
```

## Examples of Apps

| App | Agents | Pipeline | MCP servers |
|-----|--------|----------|-------------|
| `sdd-pipeline` | spec-writer, architect, coder, reviewer, QA, acceptance | full SDD flow | filesystem |
| `github-pr-reviewer` | analyzer, reviewer, comment-writer | pr-review | github, filesystem |
| `telegram-standup-bot` | standup-collector, summarizer | daily standup | telegram, notion |
| `code-onboarding` | explorer, documenter, Q&A | onboarding | filesystem, deepwiki |
| `security-audit` | scanner, analyst, reporter | audit | filesystem, github |
| `release-notes` | changelog-reader, writer | release | github |

## Difference from Individual Agents

| | Agent | App |
|--|-------|-----|
| Unit | Single agent `.md` | Bundle: agents + pipeline + MCP |
| Scope | One capability | One complete use case |
| Wiring | Manual | Automatic |
| Entry point | User invokes manually | Pipeline triggered (webhook, schedule, command) |
| Distribution | marketplace agents/ | marketplace apps/ |

## Relation to Existing Concepts

- **Claude Code plugin** — closest analogy. Bundles agents + commands + hooks + MCP. iEvo App is a Claude Code plugin variant with pipelines as first-class citizens.
- **OpenClaw skills** — similar concept but without pipelines. 5,700 skills in marketplace proves the flywheel works.
- **VSCode extensions** — same idea at IDE level: bundle functionality, install from marketplace, works immediately.

## App Marketplace

Apps live in `src/ievo/marketplace/apps/` (bundled) and the remote marketplace registry.

```
ievo list --apps          # browse available apps
ievo install <app>        # deploy agents + pipeline + MCP
ievo uninstall <app>      # clean removal
ievo update <app>         # update all components
```

## Why

Individual agents are Lego bricks. Apps are assembled kits — the user gets a working product, not parts. This is the "Apple experience" principle: install and go. Apps also make the marketplace more valuable — a complete PR review system is more compelling than three unconnected agents.

## Open Questions

- [ ] How does app versioning interact with individual agent versioning?
- [ ] Can an app depend on another app?
- [ ] App-level credentials: does the app declare required credentials, and iEvo prompts on install?
- [ ] Pipeline trigger model: how does an app's pipeline get triggered (command, webhook, schedule)?
- [ ] App isolation: do apps share agents or each app has its own copies?

## Related

- **IDEA-020**: App Composition — Teams (apps compose into teams — read this next)
- **IDEA-017**: Provider-agnostic architecture (UAF format for agents inside apps)
- **IDEA-016**: Smart spec pipeline (SDD pipeline = first built-in app)
- **PROP-2026-03-04-plugin-system.md** (apps extend the plugin system)
- **PROP-2026-03-04-universal-orchestration-architecture.md**
