メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed spec refresh, cross-session memory (trellis mem) generated by trellis init, or AI-facing bundled skills (trellis-channel, trellis-session-insight, trellis-spec-bootstrap) and bundled-skill auto-dispatch flow.
Create a Trellis migration manifest and matching docs-site changelogs for a target release by analyzing commits since the previous release. Use when preparing a patch, beta, rc, or minor release manifest.
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.
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.
Guide requirements discovery for a Trellis task after task-creation consent. Use when the user is ready to clarify requirements before implementation.
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.
| name | trellis-continue |
| description | 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.
python3 ./.trellis/scripts/get_context.py
Confirms: current task, git state, recent commits.
python3 ./.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 (only the seed _example 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:
python3 ./.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.