菜单
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.
用 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 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.
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-spec |
| description | 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. |
Sequentially implement each unchecked behavior from a spec file using TDD. Mark each behavior as done in the spec file after successful implementation.
Read the spec file provided by the user. Extract all behaviors — lines matching - [ ] **<title>** followed by a Given/When/Then description. Skip already-checked behaviors (- [x]).
List the unchecked behaviors to the user and ask for confirmation before starting. Example:
Found 5 unchecked behaviors in .specs/AMP-3166.md:
1. Create a workflow with a single signer
2. Reject workflow without signers
3. ...
Implement all of them sequentially?
For each unchecked behavior, in order:
- [ ] to - [x] on the corresponding lineAfter all behaviors are implemented, report:
Behaviors in the spec file follow this structure:
## Behaviors
### <Group name>
- [ ] **<Short behavior title>**
Given <precondition>, when <action>, then <expected outcome>
- [x] **<Already implemented title>**
Given <precondition>, when <action>, then <expected outcome>
To mark a behavior as done, replace - [ ] with - [x] on the checkbox line only.