spec-batch

Generate requirements.md, design.md, and tasks.md from a detailed input file.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/LeeHusung/harness --skill spec-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-batch
Source: https://github.com/LeeHusung/harness/tree/main/.claude/skills/spec-batch
Command: npx skills add https://github.com/LeeHusung/harness --skill spec-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec Batch automates the creation of requirements.md, design.md, and tasks.md from a detailed input file, eliminating manual drafting and reducing review cycles.

Core Features & Use Cases

  • Generates three spec artifacts in a single pass: requirements.md, design.md, and tasks.md.
  • Records Ambiguities and Assumptions in a dedicated section to ensure traceability and reviewer awareness.
  • Supports a non-interactive workflow that completes end-to-end spec generation without intermediate STOP.

Quick Start

Provide a detailed requirements input file and invoke the batch skill to automatically generate requirements.md, design.md, and tasks.md in one pass.

Frequently Asked Questions about spec-batch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate requirements, design, and tasks documents from a single input?

To automatically generate requirements, design, and tasks documents, you provide a detailed input file to trigger a non-interactive workflow that produces requirements.md, design.md, and tasks.md in a single pass.

What is the best way to handle ambiguity when creating product specifications?

Handling ambiguity during product specification creation involves recording assumptions and ambiguities in a dedicated section, ensuring traceability and reviewer awareness without interrupting the generation workflow.

How do I scope an MVP by converting requirements into system design and task decomposition?

Scoping an MVP by converting requirements into system design and tasks is done by applying automated batch processing to decompose inputs into requirements.md, design.md, and tasks.md end-to-end.

Can I generate end-to-end spec artifacts without intermediate interactive prompts?

Generating end-to-end spec artifacts without interactive prompts is supported by a non-interactive workflow that completes the full requirements, design, and tasks generation without intermediate stops.

Does spec generation work without manual drafting for each individual document?

Spec generation works without manual drafting by automating the transformation of a detailed input file into the three required artifacts, eliminating the need to manually draft each document and reducing review cycles.