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.