菜单
Initialize a project for Trellis by creating trellis.json, the specs directory, and guidelines. Use when setting up Trellis for the first time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute a Trellis task list by dispatching each task to a Claude Code subagent in its own context window. Use when the user says "build with sub-agents", "build with subagents", or when a feature has 5-20 tasks with dependencies between them. Reads `.specs/<feature>/tasks.md` produced by the tasks skill. Each subagent gets focused context (guidelines + plan + task + learnings) and returns results to the orchestrating session. Supports parallel execution of independent tasks via background subagents with worktree isolation.
Execute a Trellis task list using Claude Code's /batch command for bulk, patterned changes across many files. Use when the user says "build with batch" or when a feature involves repetitive changes across dozens or hundreds of files (e.g., migrating from one library to another, applying naming conventions, adding error handling patterns). Reads `.specs/<feature>/tasks.md` produced by the tasks skill. Translates the task list into one or more /batch invocations with worktree-isolated parallel agents.
Creates or updates .specs/guidelines.md with project-wide stack, conventions, and principles. Use when starting a project or when a fundamental technology decision has changed.
Use when user wants to Creates a pitch document at .specs/{feature}/pitch.md defining a problem domain with constraints, appetite, and solution shape. Use to frame a feature before writing a spec.
Use when user wants to Creates a technical plan at .specs/{feature}/plan.md translating a spec's functional requirements into architecture, technology, and code decisions.
Use when user wants to Creates a lightweight experiment document at .specs/sketches/{slug}.md to test a technical hypothesis before committing to a larger initiative.
| name | trellis:init |
| description | Initialize a project for Trellis by creating trellis.json, the specs directory, and guidelines. Use when setting up Trellis for the first time. |
| allowed-tools | Read, Write, Bash(mkdir:*) |
Initialize a project for Trellis by creating trellis.json and the specs directory, then run /trellis:guidelines to establish project guidelines.
Recommended effort: minimal. Single question, two file operations, then hand off to guidelines.
Check whether trellis.json exists at the project root.
trellis.json does not existAsk the user: "Where should Trellis store spec artifacts? The default is .specs/ — press Enter to accept or provide a custom path (e.g., docs/specs, design)."
Write their choice (or the default) to trellis.json at the project root:
{
"specsDir": ".specs"
}
Create the specs directory if it doesn't exist.
Confirm to the user: "Trellis initialized — specs directory set to <specsDir>/."
trellis.json already existsRead specsDir from it. Confirm to the user: "Trellis is already initialized — specs directory is <specsDir>/."
Create the specs directory if it doesn't exist.
Do not re-ask or overwrite.
After trellis.json and the specs directory are in place, run the /trellis:guidelines skill to create or update project guidelines.