planner-spec-draft

スター13

フォーク1

更新日2026年4月6日 02:10

Internal Auto-Harness planning skill for spec and design-direction drafting. Use only inside the Planner subagent when it is updating intake.md and producing spec.md plus design-direction.md.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

redker56

redker56/auto-harness

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Planner Spec Draft

This skill governs Spec Draft Mode for Auto-Harness.

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

.harness/intake.md
.harness/status.md
.harness/spec.md when revising an existing spec.
.harness/design-direction.md when revising an existing design direction.

Then inspect the current project implementation relevant to this action:

Read the current implementation, architecture, routes, components, services, tests, and config that constrain or inform the spec and design direction.
Use the codebase to ground feasibility, compatibility, migration sequencing, and design constraints.

Then read these skill references:

references/protocols/file-ownership.md
references/templates/spec-template.md
references/templates/design-direction-template.md
references/templates/status-board.md

Follow these rules:

Update .harness/intake.md first so it stays the durable decision log.
Ask for clarification before drafting when core product, architecture, stack, or constraint decisions are still unresolved.
Then write or revise .harness/spec.md and .harness/design-direction.md.
Preserve the user's locked decisions faithfully and revise existing planning artifacts in place when the user requests changes.
Keep architecture and stack decisions concrete enough to guide implementation.
Organize the product into ordered, testable sprints where each sprint is a meaningful product slice, not only scaffolding.
Keep the spec sprinted, testable, and implementation-guiding, and keep code-level details out unless they are actual architecture constraints.
Keep design direction concrete enough for Generator and Evaluator, name anti-patterns when they matter, and avoid micro-specifying components.

このリポジトリの他の Skills

同じリポジトリ

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-spec-draft
description	Internal Auto-Harness planning skill for spec and design-direction drafting. Use only inside the Planner subagent when it is updating intake.md and producing spec.md plus design-direction.md.
user-invocable	false

Planner Spec Draft

This skill governs Spec Draft Mode for Auto-Harness.

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

.harness/intake.md
.harness/status.md
.harness/spec.md when revising an existing spec.
.harness/design-direction.md when revising an existing design direction.

Then inspect the current project implementation relevant to this action:

Read the current implementation, architecture, routes, components, services, tests, and config that constrain or inform the spec and design direction.
Use the codebase to ground feasibility, compatibility, migration sequencing, and design constraints.

Then read these skill references:

references/protocols/file-ownership.md
references/templates/spec-template.md
references/templates/design-direction-template.md
references/templates/status-board.md

Follow these rules:

Update .harness/intake.md first so it stays the durable decision log.
Ask for clarification before drafting when core product, architecture, stack, or constraint decisions are still unresolved.
Then write or revise .harness/spec.md and .harness/design-direction.md.
Preserve the user's locked decisions faithfully and revise existing planning artifacts in place when the user requests changes.
Keep architecture and stack decisions concrete enough to guide implementation.
Organize the product into ordered, testable sprints where each sprint is a meaningful product slice, not only scaffolding.
Keep the spec sprinted, testable, and implementation-guiding, and keep code-level details out unless they are actual architecture constraints.
Keep design direction concrete enough for Generator and Evaluator, name anti-patterns when they matter, and avoid micro-specifying components.