claude/skills/implement-linear-issue/SKILL.md
Implement a Linear issue by breaking its acceptance criteria into tasks, implementing each with TDD, and updating the Linear issue status when done. Use when the user says 'implement issue ...', 'implement TEAM-123', or wants to implement a Linear issue.
npx skillsauth add b-galati/dotfiles implement-linear-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement a Linear issue by breaking its acceptance criteria into internal tasks, implementing each sequentially using TDD, and updating the Linear issue only after all tasks are complete.
Ask the user for the Linear issue identifier (e.g., TEAM-123). Fetch the issue and extract:
Break the acceptance criteria into an ordered list of implementation tasks. Use TaskCreate to track each one internally. Do NOT update the Linear issue yet.
Present the task list to the user and ask for confirmation before starting. Example:
Implementing TEAM-456: Add email validation to signer creation
Tasks:
1. Validate email format on signer creation
2. Return 422 with error details for invalid email
3. Reject duplicate emails within the same workflow
Implement all sequentially?
For each task, in order:
TaskUpdateTaskUpdateOnly after ALL tasks are successfully implemented:
testing
TDD workflow - Write a failing test, then implement Super Green
development
OpenAPI specification expert for creating, improving, and validating clear, self-documenting API specs. Use when designing, reviewing, or refactoring OpenAPI/Swagger specs for clarity, consistency, and usability.
testing
Implement behaviors from a specification file produced by the local-create-spec skill. Use when the user says 'implement behaviors from ...', 'implement the spec', 'implement spec ...', or wants to implement a .specs/ markdown file containing Given/When/Then behaviors with checkboxes.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".