spec-harness-spec

Convert unstructured product briefs into structured spec.md files with testable acceptance criteria.

28|2|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/chohra-med/expo_boilerplate --skill spec-harness-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-harness-spec
Source: https://github.com/chohra-med/expo_boilerplate/tree/main/.claude/skills/spec-harness-spec
Command: npx skills add https://github.com/chohra-med/expo_boilerplate --skill spec-harness-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vague, unstructured product briefs cause team misalignment, unnecessary rework, and inconsistent output from AI coding tools that lack clear, testable requirements to reference.

Core Features & Use Cases

  • Structured Spec Generation: Creates a spec.md file with testable acceptance criteria, grounded in your project's memory bank and existing component index to reuse existing work and avoid redundant definitions.
  • SDD Workflow Integration: Aligns with spec-driven development principles, adhering to your repo's ratcheted rule system, separate verifier step, and learning loop to ensure specs meet quality and consistency standards.
  • Use Case: For example, if you have a rough brief for a new user onboarding flow, this skill will generate a structured spec that references your existing auth and navigation components, giving developers and AI tools unambiguous requirements to build from.

Quick Start

Use the spec-harness-spec skill to turn your rough brief for the new payment flow feature into a structured, testable spec.md.

Frequently Asked Questions about spec-harness-spec

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

FAQPage Schema
How do I turn rough product briefs into structured software specifications?

Spec-driven development requires generating a spec.md file containing unambiguous, testable acceptance criteria. This mechanism grounds vague product requirements in your project's memory bank and component index to ensure alignment.

How do I generate testable acceptance criteria from a vague feature request?

Generating testable acceptance criteria from a vague feature request involves mapping the unstructured brief against your existing codebase. This creates verifiable specifications that reference current components to prevent redundant definitions and reduce rework.

Can I align new product requirements with an existing codebase component index?

Spec-driven development requires generating a spec.md file containing unambiguous, testable acceptance criteria. This mechanism grounds vague product requirements in your project's memory bank and component index to ensure alignment.

Does spec-driven development work with ratcheted rule systems and verifier workflows?

Spec-driven development requires generating a spec.md file containing unambiguous, testable acceptance criteria. This mechanism grounds vague product requirements in your project's memory bank and component index to ensure alignment.

Why do unstructured product briefs cause AI coding tool inconsistencies?

Spec-driven development requires generating a spec.md file containing unambiguous, testable acceptance criteria. This mechanism grounds vague product requirements in your project's memory bank and component index to ensure alignment.

What is the best way to write software specifications for AI coding tools?

Spec-driven development requires generating a spec.md file containing unambiguous, testable acceptance criteria. This mechanism grounds vague product requirements in your project's memory bank and component index to ensure alignment.