用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/joelanford/library-olm --skill sdd-implement命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | sdd-implement |
| description | Implement a work item from its spec. |
Implement a work item from its spec.
If the user provided input via $ARGUMENTS, use that to find the spec directory.
Otherwise, list specs/YYYY-MM-DD-*/ directories with status: ready or status: in-progress in their README.md frontmatter. Use AskUserQuestion to ask which one to implement.
Read all files in the work item's spec directory:
README.md — summary and designrequirements.md — functional requirements and acceptance criteriaplan.md — implementation planverification.md — verification criteriaIf the spec is incomplete (still an idea or missing files), stop and tell the user to run /sdd-plan-next-phase to refine it first.
Set the frontmatter status: in-progress in the work item's README.md.
Follow the implementation plan in plan.md task groups in order. For each task group:
specs/mission.md for design principles and specs/tech-stack.md for technical guidance.go test ./... to verify nothing is broken.specs/conventions.md. Each commit should be minimal — containing only the changes necessary for its logical unit of work — and must pass all tests independently.After implementation is complete:
verification.md and confirm it passes.requirements.md and confirm it is met.go test ./... and go vet ./... one final time.Review whether anything learned during implementation should be reflected in global SDD documents (specs/mission.md, specs/tech-stack.md, specs/conventions.md, CLAUDE.md, or any other top-level specs). If updates are needed, make them in a dedicated commit separate from the implementation commits.
Suggest the user run /sdd-review to review the changes for correctness and consistency before shipping.