dev.implement

Automate Linear task lifecycle with claim, implementation, and closure enforcement.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.implement
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/dev.implement
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces a disciplined, end-to-end workflow for Linear tasks, ensuring claiming, implementation, and mandatory closure documentation to maintain strong audit trails.

Core Features & Use Cases

  • Phase-based workflow enforcement from claim to closure.
  • Mandatory closure artifacts including closure comments, status updates, and linked commits.
  • Context-aware execution using task selectors and project mappings to ensure traceability.

Quick Start

Use the skill to process a Linear task by running /dev.implement, select a ready task, perform implementation, and close with proper documentation.

Frequently Asked Questions about dev.implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce traceable closure for Linear tasks on a feature branch?

Linear task closure is enforced by automating the claim, implementation, and closure phases, requiring linked commits and mandatory closure comments via Linear MCP integration to maintain a strong audit trail.

What is needed to automate the Linear task lifecycle from claim to closure?

Automating the Linear task lifecycle requires a local .linear-mapping.json file, tasks.md mappings, and Linear MCP integration to execute context-aware status updates and enforce Phase 4 closure documentation.

How do I execute Linear tasks with mandatory closure documentation?

To execute Linear tasks with mandatory closure, run the implementation command, select a ready task from your feature branch, perform the implementation, and close it with formal status updates and linked commits.

Does the Linear task workflow require a specific mapping configuration?

Yes, the Linear task workflow requires a specific mapping configuration using a local .linear-mapping.json file and tasks.md mappings to ensure context-aware execution and traceable task selectors.

Why does Phase 4 closure matter for Linear task traceability?

Phase 4 closure matters for traceability because it mandates closure artifacts including status updates, closure comments, and linked commits, ensuring a disciplined end-to-end audit trail for feature branch implementation.