メニュー
Run the project's test suite, add tests for each task's acceptance criteria, and emit a tests.md summary. Use when the orchestrator routes the tests phase. Do not use for unit-test debugging during the code phase.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Verify whether Monozukuri can run with Codex in loop or full-auto workflows by checking agent availability, skill discovery, dry-run behavior, and the targeted Bats validation path. Use for Monozukuri Codex readiness, loop, agent doctor, or skill availability questions. Do not use for unrelated repositories or generic CI triage.
Audit a repository's local skills, agents, and instruction files for Codex compatibility and recommend only missing or redundant workflow assets. Use when the user asks whether skills are adapted to Codex, how to invoke project skills or agents, or which skills to install after scanning a repo. Do not use for ordinary code review or non-agent tooling.
Open a GitHub pull request via gh pr create with a body summarizing PRD goals, code changes, and test results. Use when the orchestrator routes the pr phase. Do not use for editing existing PRs or non-GitHub remotes.
Generate a PRD artifact for a monozukuri feature. Use when the orchestrator routes the prd phase or when the user asks to draft a feature PRD. Do not use for techspec/tasks generation or for editing an existing PRD.
Decompose a PRD and TechSpec into a structured tasks.json task list for monozukuri's code phase. Use when the orchestrator routes the tasks phase. Do not use for PRD or TechSpec generation.
Generate a TechSpec artifact that translates a PRD into a concrete implementation plan. Use when the orchestrator routes the techspec phase or when the user asks to draft a technical specification. Do not use for PRD generation or task decomposition.
| name | mz-run-tests |
| description | Run the project's test suite, add tests for each task's acceptance criteria, and emit a tests.md summary. Use when the orchestrator routes the tests phase. Do not use for unit-test debugging during the code phase. |
| version | 1.0.0 |
You are executing the tests phase of monozukuri's autonomous feature loop.
$MONOZUKURI_RUN_DIR/$MONOZUKURI_FEATURE_ID/techspec.md (§ Testing)$MONOZUKURI_RUN_DIR/$MONOZUKURI_FEATURE_ID/code.md$MONOZUKURI_RUN_DIR/$MONOZUKURI_FEATURE_ID/tasks.jsonCLAUDE.md, AGENTS.md, or the monozukuri learning store$MONOZUKURI_WORKTREEWrite $MONOZUKURI_RUN_DIR/$MONOZUKURI_FEATURE_ID/tests.md with:
tests.md — do not write new tests.tasks.json must have at least one corresponding test.test($MONOZUKURI_FEATURE_ID): add tests for <short description>tasks.json, write tests covering each acceptance_criteria item.tests.md with the summary.Before starting, read $MONOZUKURI_MEMORY_DIR/MEMORY.md for shared context (e.g., test framework conventions noted during the code phase). After writing tests.md, update $MONOZUKURI_TASK_MEMORY with pass/fail counts and any flaky tests identified. If $MONOZUKURI_NEEDS_COMPACTION is non-empty and not none, run the mz-workflow-memory skill to compact memory files before continuing.