菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reconstitue un résumé de ce que l'utilisateur a fait sur une journée donnée en croisant ses emails (Gmail), Slack, Linear et GitLab. Utilise ce skill dès que l'utilisateur demande un récap/résumé de sa journée, de sa semaine ou d'un jour précis — par exemple "résume ce que j'ai fait hier", "fais-moi un point sur ma journée", "qu'est-ce que j'ai fait lundi ?", "recap de la semaine" — même s'il ne mentionne aucune source explicitement.
Create GitLab merge requests with intelligent title and description generation from git commits. Supports stacked MRs by targeting the parent branch (falls back to main). Use when you want to create an MR and need to generate a clear title following git conventions and auto-populate the description from commit messages.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
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.
Break a Design-Document (DD) into independently-grabbable Linear issues using tracer-bullet vertical slices. Use when user wants to convert a DD to issues, create implementation tickets, or break down a DD into work items.
This skill should be used when the user asks to create a spec, a specification, or to formalize requirements. It accepts any input (Linear issue, free text, file, URL, etc.), explores the codebase to identify impacts and required changes, then collaboratively produces a behavior-driven specification with toggleable behaviors that map directly to automated tests.
| name | implement-linear-issue |
| description | 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. |
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: