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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Read the relevant development guidelines before starting your task.
Execute these steps:
Read current task artifacts:
prd.md for requirements and acceptance criteriadesign.md if present for technical designimplement.md if present for execution order and validation planDiscover packages and their spec layers:
python ./.trellis/scripts/get_context.py --mode packages
Identify which specs apply to your task based on:
cli/, docs-site/)Read the spec index for each relevant module:
cat .trellis/spec/<package>/<layer>/index.md
Follow the "Pre-Development Checklist" section in the index.
Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md). Read those files to understand the coding standards and patterns.
Always read shared guides:
cat .trellis/spec/guides/index.md
For a non-trivial task, state the change boundary before writing code. Non-trivial means it touches more than one file, crosses a layer, changes a public interface, or edits code you did not just write. Write down:
A small, well-scoped change does not need this — do it directly.
If the real scope turns out to be clearly larger than this, say so and why before continuing. Do not widen the change on your own.
Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.