planner-clarify

Estrelas13

Forks1

Atualizado6 de abril de 2026 às 02:10

Internal Auto-Harness planning skill for clarification intake. Use only inside the Planner subagent when it is producing .harness/intake.md and .harness/status.md.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

redker56

redker56/auto-harness

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

Explorador de arquivos

12 arquivos

SKILL.md

readonly

name	planner-clarify
description	Internal Auto-Harness planning skill for clarification intake. Use only inside the Planner subagent when it is producing .harness/intake.md and .harness/status.md.
user-invocable	false

Planner Clarify

This skill governs Clarification Mode for Auto-Harness.

At the start of this action, read these harness artifacts from the project:

.harness/intake.md when it already exists.
.harness/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:

Read the current app structure, entrypoints, routes, components, services, tests, and config that define the existing constraints or compatibility surface.
Use the codebase to understand current reality and constraints; do not infer sprint scope, named defects, or implementation commitments from it.

Then read these skill references:

references/protocols/file-ownership.md
references/clarification/core.md
references/clarification/product.md
references/clarification/architecture.md
references/clarification/stack.md
references/clarification/constraints.md
references/catalogs/architecture-options.md
references/catalogs/consistency-patterns.md
references/catalogs/frontend-patterns.md
references/catalogs/stack-options.md
references/templates/intake-template.md

Follow these rules:

Write only .harness/intake.md and .harness/status.md.
Produce a relay-ready numbered clarification questionnaire for the Orchestrator.
Do not draft .harness/spec.md or .harness/design-direction.md.
If the user has not explicitly answered a clarification item, keep it unresolved rather than inferring it from the brief.

Mais deste repositório

mesmo repositório

evaluator-review-contract-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

2026-05-0213

evaluator-write-final-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.

2026-05-0213

evaluator-write-qa-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluator_qa_parallel.

2026-05-0213

evaluator-write-retest-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluator_retest_parallel.

2026-05-0213

generator-build-integrator

redker56/auto-harness

Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.

2026-05-0213

generator-build-worker

redker56/auto-harness

Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.

2026-05-0213

name	planner-clarify
description	Internal Auto-Harness planning skill for clarification intake. Use only inside the Planner subagent when it is producing .harness/intake.md and .harness/status.md.
user-invocable	false

Planner Clarify

This skill governs Clarification Mode for Auto-Harness.

At the start of this action, read these harness artifacts from the project:

.harness/intake.md when it already exists.
.harness/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:

Read the current app structure, entrypoints, routes, components, services, tests, and config that define the existing constraints or compatibility surface.
Use the codebase to understand current reality and constraints; do not infer sprint scope, named defects, or implementation commitments from it.

Then read these skill references:

references/protocols/file-ownership.md
references/clarification/core.md
references/clarification/product.md
references/clarification/architecture.md
references/clarification/stack.md
references/clarification/constraints.md
references/catalogs/architecture-options.md
references/catalogs/consistency-patterns.md
references/catalogs/frontend-patterns.md
references/catalogs/stack-options.md
references/templates/intake-template.md

Follow these rules:

Write only .harness/intake.md and .harness/status.md.
Produce a relay-ready numbered clarification questionnaire for the Orchestrator.
Do not draft .harness/spec.md or .harness/design-direction.md.
If the user has not explicitly answered a clarification item, keep it unresolved rather than inferring it from the brief.