Menu
Internal Auto-Harness planning skill for parallel clarification intake. Use only inside the Planner subagent when it is producing .harness-parallel/intake.md and .harness-parallel/status.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.
Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluator_qa_parallel.
Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluator_retest_parallel.
Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.
Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.
| name | planner-clarify-parallel |
| description | Internal Auto-Harness planning skill for parallel clarification intake. Use only inside the Planner subagent when it is producing .harness-parallel/intake.md and .harness-parallel/status.md. |
| user-invocable | false |
This skill governs Clarification Mode for the parallel Auto-Harness workflow.
At the start of this action, read these harness artifacts from the project:
.harness-parallel/intake.md when it already exists..harness-parallel/status.md when it already exists.Then inspect the current project implementation only when the brief points to an existing project, codebase, or migration surface:
Then read the same reference files used by skills/planner-clarify/, including its clarification guides, catalogs, file-ownership protocol, and intake template. Apply those rules to .harness-parallel/ paths.
Follow these rules:
.harness-parallel/intake.md and .harness-parallel/status.md.workflow_mode=parallel and pending_action=brief_clarification_parallel in .harness-parallel/status.md..harness-parallel/spec.md or .harness-parallel/design-direction.md..harness/.