@mindfoldhq/trellis

A multi-platform AI coding framework that rules
_{Supports Claude Code, Cursor, OpenCode, iFlow, Codex, Kilo, Kiro, Gemini CLI, Antigravity, and Qoder.}

简体中文 • Docs • Quick Start • Supported Platforms • Use Cases

Why Trellis?

Capability	What it changes
Auto-injected specs	Write conventions once in .trellis/spec/, then let Trellis inject the relevant context into each session instead of repeating yourself.
Task-centered workflow	Keep PRDs, implementation context, review context, and task status in .trellis/tasks/ so AI work stays structured.
Parallel agent execution	Run multiple AI tasks side by side with git worktrees instead of turning one branch into a traffic jam.
Project memory	Journals in .trellis/workspace/ preserve what happened last time, so each new session starts with real context.
Team-shared standards	Specs live in the repo, so one person’s hard-won workflow or rule can benefit the whole team.
Multi-platform setup	Bring the same Trellis structure to 10 AI coding platforms instead of rebuilding your workflow per tool.

Quick Start

# 1. Install Trellis
npm install -g @mindfoldhq/trellis@latest

# 2. Initialize in your repo
trellis init -u your-name

# 3. Or initialize with the platforms you actually use
trellis init --cursor --opencode --codex -u your-name

• -u your-name creates .trellis/workspace/your-name/ for personal journals and session continuity.
• Platform flags can be mixed and matched. Current options include --cursor, --opencode, --iflow, --codex, --kilo, --kiro, --gemini, --antigravity, and --qoder.
• For platform-specific setup, entry commands, and upgrade paths, use the docs: Quick Start • Supported Platforms • Real-World Scenarios

Use Cases

Teach AI your project once

Put coding standards, file structure rules, review habits, and workflow preferences into Markdown specs. Trellis loads the relevant pieces automatically so you do not have to re-explain the repo every time.

Run multiple AI tasks in parallel

Use git worktrees and Trellis task structure to split work cleanly across agents. Different tasks can move forward at the same time without stepping on each other’s branches or local state.

Turn project history into usable memory

Task PRDs, checklists, and workspace journals make previous decisions available to the next session. Instead of starting from blank context, the next agent can pick up where the last one left off.

Keep one workflow across tools

If your team uses more than one AI coding tool, Trellis gives you one shared structure for specs, tasks, and process. The platform-specific wiring changes, but the workflow stays recognizable.

How It Works

Trellis keeps the core workflow in .trellis/ and generates the platform-specific entry points you need around it.

.trellis/
├── spec/                    # Project standards, patterns, and guides
├── tasks/                   # Task PRDs, context files, and status
├── workspace/               # Journals and developer-specific continuity
├── workflow.md              # Shared workflow rules
└── scripts/                 # Utilities that power the workflow

Depending on the platforms you enable, Trellis also creates tool-specific integration files such as .claude/, .cursor/, AGENTS.md, .agents/, .kilocode/, and .kiro/.

At a high level, the workflow is simple:

• Define standards in specs.
• Start or refine work from a task PRD.
• Let Trellis inject the right context for the current task.
• Use checks, journals, and worktrees to keep quality and continuity intact.

Spec Templates & Marketplace

Specs ship as empty templates by default — they are meant to be customized for your project's stack and conventions. You can fill them from scratch, or start from a community template:

# Fetch templates from a custom registry
trellis init --registry https://github.com/your-org/your-spec-templates

Browse available templates and learn how to publish your own on the Spec Templates page.

What's New

• v0.3.6: task lifecycle hooks, custom template registries (--registry), parent-child subtasks, fix PreToolUse hook for CC v2.1.63+.
• v0.3.5: hotfix for delete migration manifest field name (Kilo workflows).
• v0.3.4: Qoder platform support, Kilo workflows migration, record-session task awareness.
• v0.3.1: background watch mode for trellis update, improved .gitignore handling, docs refresh.
• v0.3.0: platform support expanded from 2 to 10, Windows compatibility, remote spec templates, /trellis:brainstorm.

FAQ

How is this different from CLAUDE.md, AGENTS.md, or .cursorrules?

Those files are useful, but they tend to become monolithic. Trellis adds structure around them: layered specs, task context, workspace memory, and platform-aware workflow wiring.

Is Trellis only for Claude Code?

No. Trellis currently supports Claude Code, Cursor, OpenCode, iFlow, Codex, Kilo, Kiro, Gemini CLI, and Antigravity. The detailed setup and entry command for each tool lives in the supported platforms guide.

Do I have to write every spec file manually?

No. Many teams start by letting AI draft specs from existing code and then tighten the important parts by hand. Trellis works best when you keep the high-signal rules explicit and versioned.

Can teams use this without constant conflicts?

Yes. Personal workspace journals stay separate per developer, while shared specs and tasks stay in the repo where they can be reviewed and improved like any other project artifact.

Star History

Community & Resources

• Official Docs - Product docs, setup guides, and architecture
• Quick Start - Get Trellis running in a repo fast
• Supported Platforms - Platform-specific setup and command details
• Real-World Scenarios - See how the workflow plays out in practice
• Changelog - Track current releases and updates
• Tech Blog - Product thinking and technical writeups
• GitHub Issues - Report bugs or request features
• Discord - Join the community

Official Repository • AGPL-3.0 License • Built by Mindfold