菜单
Second Build-phase skill for pi-forge. Use to implement the plan with strict test-first discipline by delegating to superpowers:test-driven-development. Reads artifacts/plan.md and brief.json, implements each acceptance criterion red-green-refactor, and makes conventional commits.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Test-phase skill for pi-forge. Use during the Test phase to run the project's test suites (unit, integration, contract, E2E for the general path), capture results and coverage, write artifacts/test-report.md, and record metrics via forge_metric.
Safe bridge to the cxas CLI for pi-forge CXAS projects. Use whenever a CX Agent Studio project needs to lint an app directory, run evaluations, manage apps/deployments, or migrate from Dialogflow CX. Always go through the forge_cxas tool (never raw shell); it enforces an allow-list and returns structured results.
Evaluate-phase skill for pi-forge. Use during the Evaluate phase to make a holistic, freeform judgment of the work against the brief, write artifacts/scorecard.md with an approve|iterate recommendation plus justification and risks, and record the verdict via forge_metric to inform the G2 gate.
First Build-phase skill for pi-forge. Use at the start of the Build phase to turn the approved brief into an executable plan. Reads artifacts/brief.json and writes artifacts/plan.md with the approach, module/feature breakdown (WBS), build sequence, and stack rationale.
Drives a project through the pi-forge delivery lifecycle (intake → clarify → build → test → evaluate → improve → deliver). Use when starting or continuing a pi-forge project, or whenever asked to "run the project", "continue the project", or after /forge-new. Reads state via forge_status and advances phases via forge_advance, opening gates with forge_gate.
Improve-phase skill for pi-forge. Use during the Improve phase after an iterate verdict to root-cause the scorecard findings, write a prioritized artifacts/backlog.md, and hand back so the orchestrator re-enters the Build phase (bounded by maxIterations).
| name | tdd-builder |
| description | Second Build-phase skill for pi-forge. Use to implement the plan with strict test-first discipline by delegating to superpowers:test-driven-development. Reads artifacts/plan.md and brief.json, implements each acceptance criterion red-green-refactor, and makes conventional commits. |
Implement the plan with test-first discipline. Drive transitions only through forge_* tools.
artifacts/plan.md and artifacts/brief.json.superpowers:test-driven-development skill and follow it: write the failing test, watch it fail, implement minimally, watch it pass, refactor.forge_note.superpowers:test-driven-development is unavailable in this environment, say so explicitly and fall back to manual test-first: write the failing test, see it fail, implement, see it pass. Never silently skip tests.