菜单
Implement one behavior at a time with a red-green-refactor loop. Use when: executing tasks.md, doing TDD, implementing a feature from specs. Do not use: for test planning, bulk implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | vertical-tdd |
| description | Implement one behavior at a time with a red-green-refactor loop. Use when: executing tasks.md, doing TDD, implementing a feature from specs. Do not use: for test planning, bulk implementation. |
Use one behavior as the unit of progress. Run only after the user has approved the spec.
spec.md, plan.md, and tasks.md in the feature folder.- [ ] or continue - [~] in progress. Mark the
task - [~] when starting and - [x] when done.unit, integration, or both) and the
spec's Test Strategy. If missing, decide using the same rules as
test generation reference.status: Implemented in spec.md frontmatter and update the row in specs/README.md.- [x] in tasks.md, clear any stale
- [~], and annotate or mark done any plan.md item fully delivered. Do
not declare work complete with stale checkboxes.tasks.md checkboxes as each task starts ([~]) and finishes ([x]).
Stale checkboxes block reliable resumption from specs/README.md and the
feature folder.Create or revise coding-assistant skills that match this repository's structure and conventions. Use when: writing, renaming, or reviewing a skill. Do not use: for general writing or non-skill documentation.
Set up an Android CI/CD pipeline with lint, static analysis, unit tests, dependency review, and build verification. Use when: creating CI for Android, adding Gradle checks. Do not use: for local development setup, non-CI automation.
Run a disciplined bugfix loop with reproduction, hypotheses, regression test, fix, and cleanup. Use when: fixing bugs, debugging regressions, investigating failures. Do not use: for feature implementation, refactoring.
Design or review a ChromaDB-backed RAG workflow. Use when: creating collections, choosing embedding functions, chunking documents, writing retrievers. Do not use: for general LLM integration, non-RAG patterns.
Create, review, or debug a CI/CD workflow. Use when: editing GitHub Actions, fixing CI failures, adding release/deploy automation. Do not use: for general DevOps, infrastructure as code.
Structured code review workflow ensuring context and clarity. Use when: implementation complete, tests verified, before merge request. Do not use: during active implementation, before verification checklist, or for design reviews.