// 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.
| 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:
status=planning + no prd.md → 1.1 (load trellis-brainstorm)status=planning + prd.md exists + implement.jsonl not curated (only the seed _example row) → 1.3status=planning + prd.md + curated implement.jsonl → 1.4 (run task.py start to enter Phase 2)status=in_progress + implementation not started → 2.1status=in_progress + implementation done, not yet checked → 2.2status=in_progress + check passed → 3.1status=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 output exists (e.g., prd.md for 1.1; implement.jsonl with curated entries for 1.3) — skip themOnce 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, skill routing table, and the DO-NOT-skip table live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.
Collaborative requirements discovery session optimized for AI coding workflows. Creates task directories, seeds PRDs, runs codebase research, proposes concrete implementation approaches with trade-offs, and converges on MVP scope through structured Q&A. Use when requirements are unclear, multiple implementation paths exist, trade-offs need evaluation, or a complex feature needs scoping before development.
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.
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.
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, or workflows generated by trellis init.
Wrap up an active Trellis task: archive it (and any other completed-but-unarchived tasks the user wants to clean up) and record a session journal. Refuses to run if the working tree has uncommitted code changes (those belong in workflow Phase 3.4 first). Use when the user asks to finish / wrap up / call it a day, or invokes $finish-work.
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.