メニュー
Internal TDD refactorer fork — invoked exclusively by /dev-process-toolkit:tdd via context:fork pairing with the tdd-refactorer subagent, exactly once at end of FR after all ACs are GREEN. Do not invoke directly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement a feature or fix end-to-end. Analyzes the request, builds in TDD order, runs gate checks, self-reviews with bounded loops, and reports for human approval before committing.
Bundle the Release Checklist + /docs --commit --full into one atomic, human-approved release commit. Reads specs/plan/M<N>.md, bumps the four release files, regenerates docs, prompts once for approval, commits on `y`, does not push.
Guide the user through writing or completing spec files (requirements, technical spec, testing spec, plan). Use after /setup to fill in specs before implementation, or to update existing specs.
Set up SDD/TDD development process for the current project. Creates CLAUDE.md, configures settings, and optionally creates spec files. Use when starting a new project or adding process to an existing one.
Socratic design session for greenfield features with open solution spaces. Clarifies goals one question at a time, proposes 2-3 approaches with tradeoffs, gets design approval, then feeds into /spec-write.
Run the project gate checks and report results. Use after completing any feature, before creating a PR, or to verify project health.
| name | tdd-refactor |
| description | Internal TDD refactorer fork — invoked exclusively by /dev-process-toolkit:tdd via context:fork pairing with the tdd-refactorer subagent, exactly once at end of FR after all ACs are GREEN. Do not invoke directly. |
| context | fork |
| agent | tdd-refactorer |
| user-invocable | false |
| argument-hint | <changed-files list> |
You are running as the tdd-refactorer subagent inside a forked context spawned by /dev-process-toolkit:tdd, exactly once per FR after every AC is GREEN. You see the file list of what shipped but not the per-AC implementation reasoning.
The orchestrator passes you (in its prompt body):
```tdd-result block as the last thing in your turn.Empty refactor is fine. If there's nothing worth changing, return files: [] with a notes line.
role: refactorer
status: ok
files:
- src/foo.ts
- src/shared.ts
command: bun test
output_excerpt: |
PASS — 47 of 47
notes: hoisted shared validate() helper
Required fields: role, status, files (may be empty list), command, output_excerpt. notes is optional.
status: ok — tests still GREEN after your changes.status: failed — your refactor broke a test. Orchestrator counts this as mode C and decides retry-vs-halt per the bounded-retry budget.status: failed and explain in notes.