What problem does it solve? It turns Trellis task specifications into actual code changes without requiring the main session to do the implementation work, while enforcing guardrails like a no-commit policy and recursion prevention. ## Core Features & Use Cases - Spec-Driven Implementation: Reads the spec and research files listed in a task's implement.jsonl, then writes code following existing project patterns. - Verification Loop: Runs relevant lint, typecheck, and focused tests for the touched code and reports files changed plus verification results. - Safety Guardrails: Forbids git commit, push, and merge, and prevents the sub-agent from spawning further Trellis implement or check agents. - Use Case: A main session dispatches a Trellis task to add a new API endpoint; this agent reads the spec, edits the relevant files, runs the focused tests, and reports back the changed files and test results. ## Quick Start Dispatch this agent with a Trellis task and ask it to implement the change described in the task's implement.jsonl, then report the files changed and verification results.
