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.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Resume work on the current task — pick up at the right phase/step in .trellis/workflow.md.
python ./.trellis/scripts/get_context.py
Confirms: current task, git state, recent commits.
python ./.trellis/scripts/get_context.py --mode phase
Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.
get_context.py shows the active task's status field. Route by status + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.
status=planning + no prd.md → 1.1 (load trellis-brainstorm)status=planning + prd.md only → decide whether the task is lightweight or complex. Lightweight can move to 1.4 review; complex returns to 1.1 to add design.md + implement.md.status=planning + complex artifacts complete + sub-agent jsonl not curated (empty, or only a legacy _example placeholder row) → 1.3status=planning + required artifacts complete + required jsonl curated or inline mode → 1.4 (ask for start review; only run task.py start after user confirms)status=in_progress + implementation not started → 2.1status=in_progress + implementation done, not yet checked → 2.2status=in_progress + check passed → 3.3 (spec update) → 3.4 (commit)status=completed (rare; usually archived immediately) → archive flowPhase rules (full detail in .trellis/workflow.md):
[required] steps must not be skipped[once] steps are already done if the required output exists. prd.md alone can be enough only for lightweight tasks; complex tasks also need design.md and implement.md.Once you know which step to resume at:
python ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform codex
Follow the loaded instructions. After each [required] step completes, move to the next.
Full workflow and detailed phase steps live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
日本語の概要は準備中です。原文の説明を表示しています。