plan-draft

Draft a component plan and test harness documentation.

157|12|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/dcosson/h2 --skill plan-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-draft
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/plan-draft
Command: npx skills add https://github.com/dcosson/h2 --skill plan-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-draft converts high-level planning intent into a concrete, fully-detailed plan and accompanying test-harness documentation for a single component, preventing gaps between design and implementation.

Core Features & Use Cases

  • Generates an architecture summary, modules, interfaces, and dependency outlines for a component.
  • Produces a companion test harness document detailing verification steps and acceptance criteria.
  • Typical workflow: after a plan index is created by a plan-architect, plan-draft expands it into the complete component plan and a test harness counterpart.

Quick Start

Provide the component identifier and optional scope description to generate the plan and its test harness.

Frequently Asked Questions about plan-draft

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

FAQPage Schema
How do I generate detailed component architecture and module layout documentation?

Generate detailed component architecture and module layout documentation by providing a component identifier and optional scope notes. The tool outputs a fully detailed architecture summary, module interfaces, APIs, and dependency outlines to docs/plans/.

What's the best way to create a test harness document with acceptance criteria for a new component?

Create a test harness document with acceptance criteria by drafting a companion document alongside the component plan. It details deterministic verification steps and acceptance criteria to ensure no gaps exist between design and implementation.

Do I need a plan index before drafting component architecture and test harness docs?

Yes, you need a plan index created beforehand. The tool operates after a plan-architect has created the plan index, expanding it into a complete component plan and a test harness counterpart.

Can I use plan-draft to document APIs and dependency outlines for a single component?

Yes, you can document APIs and dependency outlines for a single component. Provide the component identifier and optional scope description to generate a fully detailed plan covering interfaces, modules, and dependency outlines.

Why does my component implementation deviate from the initial design plan?

Component implementation deviates from design plans when gaps exist between high-level planning intent and concrete documentation. Drafting a complete plan with architecture, APIs, and acceptance criteria prevents these design-implementation gaps.

What inputs are required to draft a complete component plan and test harness?

Required inputs include a component identifier and optional scope notes or description. The tool uses these inputs to generate a fully detailed architecture, module layout, APIs, acceptance criteria, and a deterministic test-harness document.