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
1520 skills26 agents8 commands5 hooks
+1

Claude Code

$ npx -y skills add redker56/auto-harness --skill planner-spec-draft --agent claude-code

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
@redker56
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.

1520 skills26 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
15
Star history of redker56/auto-harness on GitHub, a chart by star-history.com

Other skills on auto-harness.

evaluator-write-qa

evaluator-write-qa

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

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n2w209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about planner-spec-draft.

Which coding agents can use planner-spec-draft?
planner-spec-draft installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.