Skip to content
Automation
Skill

/planner-spec-draft

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.

From plugin
auto-harness
1420 skills26 agents8 commands5 hooks
+1
Install
$ npx -y skills add redker56/auto-harness --skill planner-spec-draft --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/planner-spec-draft

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

planner-spec-draft.SKILL.md
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.
Read more
Ships withauto-harness

Auto-Harness is a Claude Code plugin for longer software tasks that need planning, implementation, QA, fixes, retests, and a final report. Give it a product brief.

Get the whole plugin

Other skills on auto-harness.