issue-implementation

To claim and implement a Trellis task, use the claim_task tool to take ownership of a specific task or automatically pick the next eligible one, then follow the research-first workflow to plan and execute your coding work.

The research-first workflow requires reading the parent issue for context, verifying file paths and conventions, and planning implementation steps before writing any code, ensuring traceability and accountability throughout the task execution.

No, this skill is strictly for single task focus and cannot manage multiple tasks or epics. For multi-task features or epics, you must use the issue-implementation-orchestration skill instead to coordinate the broader workflow.

Yes, task implementation requires using claim_task, get_issue, and complete_task tools to manage task state, log progress, and track file changes while enforcing the research and planning workflow within the Trellis system.

You should not use this approach when your work spans multiple tasks, features, or epics. It applies only to individual tasks, so switch to issue-implementation-orchestration when broader project coordination is needed.

You log progress and file changes during task execution by using the related Trellis tools to manage task state and maintain logs, ensuring your implementation steps remain traceable and accountable from start to completion.