ln-401-task-executor
Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks.
When & Why to Use This Skill
The Implementation Task Executor is a specialized Claude skill designed to automate the end-to-end execution of software development tasks. It manages the full lifecycle of implementation and refactoring tickets—moving them from 'Todo' to 'To Review'—while strictly adhering to KISS/YAGNI principles and project-specific technical guides. By integrating with Linear or file-based Kanban systems, it ensures that code changes, documentation updates, and project statuses remain perfectly synchronized and traceable.
Use Cases
- Automated Feature Implementation: Executing planned features by following technical approach documents and acceptance criteria while maintaining code traceability with Task ID comments.
- Systematic Code Refactoring: Performing codebase improvements and updates, ensuring that impacted tests and documentation are updated in parallel with the logic changes.
- Project Management Synchronization: Automatically updating task statuses in Linear or local Markdown Kanban boards (e.g., moving tasks to 'In Progress' and 'To Review') as work progresses.
- Continuous Quality Enforcement: Running type-checks and linting tools automatically before marking a task as complete to ensure all deliverables meet the project's quality standards.
| name | ln-401-task-executor |
|---|---|
| description | Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks. |
Implementation Task Executor
Executes a single implementation (or refactor) task from Todo to To Review using the task description and linked guides.
Purpose & Scope
- Handle one selected task only; never touch other tasks.
- Follow task Technical Approach/plan/AC; apply KISS/YAGNI and guide patterns.
- Update Linear/kanban for this task: Todo -> In Progress -> To Review.
- Run typecheck/lint; update docs/tests/config per task instructions.
- Not for test tasks (label "tests" goes to ln-404-test-executor).
Task Storage Mode
| Aspect | Linear Mode | File Mode |
|---|---|---|
| Load task | get_issue(task_id) |
Read("docs/tasks/epics/.../tasks/T{NNN}-*.md") |
| Update status | update_issue(id, state) |
Edit the **Status:** line in file |
| Kanban | Updated by Linear sync | Must update kanban_board.md manually |
File Mode status format:
## Status
**Status:** In Progress | **Priority:** High | **Estimate:** 4h
Workflow (concise)
- Load context: Fetch full task description (Linear: get_issue; File: Read task file); read linked guides/manuals/ADRs/research; auto-discover team/config if needed.
- Receive task: Get task ID from orchestrator (ln-400); load full task description.
- Start work: Update this task to In Progress (Linear: update_issue; File: Edit status line); move it in kanban (keep Epic/Story indent).
- Implement: Follow checkboxes/plan; keep it simple; avoid hardcoded values; reuse existing components; add Task ID comment (
// See PROJ-123) to new code blocks; update docs noted in Affected Components; update existing tests if impacted (no new tests here). - Quality: Run typecheck and lint (or project equivalents); ensure instructions in Existing Code Impact are addressed.
- Finish: Mark task To Review (Linear: update_issue; File: Edit status line); update kanban to To Review; add summary comment (what changed, tests run, docs touched).
Critical Rules
- Single-task updates only; no bulk status changes.
- Keep language of the task (EN/RU) in edits/comments.
- No code snippets in the description; code lives in repo, not in Linear.
- No new test creation; only update existing tests if required.
- Preserve Foundation-First ordering from orchestrator; do not reorder tasks.
- Add Task ID comments to new code blocks for traceability (
// See PROJ-123or# See PROJ-123).
Definition of Done
- Task selected and set to In Progress; kanban updated accordingly.
- Guides/manuals/ADRs/research read; approach aligned with task Technical Approach.
- Implementation completed per plan/AC; docs and impacted tests updated.
- Typecheck and lint passed (or project quality commands) with evidence in comment.
- Task set to To Review; kanban moved to To Review; summary comment added.
Reference Files
- Guides/manuals/ADRs/research:
docs/guides/,docs/manuals/,docs/adrs/,docs/research/ - Kanban format:
docs/tasks/kanban_board.md
Version: 3.0.0 Last Updated: 2025-12-23