菜单
Generate the test suite from the spec's §5 Tests blocks — Profile A pytest (70% coverage, TECH-A-013) or Profile B smoke checklist. Trigger: after code generation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | aiws-sdd-test-generation |
| description | Generate the test suite from the spec's §5 Tests blocks — Profile A pytest (70% coverage, TECH-A-013) or Profile B smoke checklist. Trigger: after code generation. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
Turn each operation's Tests block (§5) into concrete artifacts. Pattern reference: a
PYTEST_PATTERNS.md (external; supply your own, load on demand).
{{paths.specs}}/); reject draft/retired.aiws-sdd-code-generation.tests/{unit,integration,e2e}/ mapped from the test-name hints (route happy/
error path, use-case unit, repository integration, lifecycle, external-client with httpx.MockTransport).
Shared fixtures + a [tool.coverage] block at fail_under = 70 (TECH-A-013); add only dev-deps used
(pytest, pytest-asyncio, coverage[toml]). Verify with pytest --collect-only; roll back un-collectable files.<h2>-per-operation checklist to tests/smoke.test.html; verify it parses.Does not execute tests, modify source, or invent assertions (provides scaffolding; the user fills unique
assertions). Record the run in {{paths.changes}}/<change>/. Hand off to aiws-sdd-self-review.
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.