Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Initialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent compact context by following these steps.
Identity, git status, current task, active tasks, journal location.
python ./.trellis/scripts/get_context.py
If this output includes a line beginning Trellis update available:, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.
Compact Phase Index, request triage rules, planning artifact contract, and the step-detail command.
python ./.trellis/scripts/get_context.py --mode phase
Full guide in .trellis/workflow.md (read on demand).
Discover packages + spec layers, then read each relevant index file.
python ./.trellis/scripts/get_context.py --mode packages
cat .trellis/spec/guides/index.md
cat .trellis/spec/<package>/<layer>/index.md # for each relevant layer
Index files list the specific guideline docs to read when you actually start coding.
From Step 1 you know the current task and status. Check the task directory:
planning + no prd.md → Phase 1.1. Load the trellis-brainstorm skill.planning + prd.md exists → stay in Phase 1. Lightweight tasks can be PRD-only; complex tasks need design.md + implement.md. Load the relevant Phase 1 step detail before task.py start.in_progress → Phase 2 step 2.1. Load the step detail:
python ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex
| User intent | Skill |
|---|---|
| New feature / unclear requirements | trellis-brainstorm |
| About to write code | trellis-before-dev |
| Done coding / quality check | trellis-check |
| Stuck / fixed same bug multiple times | trellis-break-loop |
| Learned something worth capturing | trellis-update-spec |
Full rules + anti-rationalization table in .trellis/workflow.md.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
日本語の概要は準備中です。原文の説明を表示しています。
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
日本語の概要は準備中です。原文の説明を表示しています。
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Resume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.
日本語の概要は準備中です。原文の説明を表示しています。