Write a scoped spec with goals, non-goals, and acceptance criteria before implementation.
npx skills add https://github.com/t0lab/harness-kit --skill spec-driven-t0lab
Please help me install this Agent Skill. Skill: spec-driven Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/spec-driven Command: npx skills add https://github.com/t0lab/harness-kit --skill spec-driven-t0lab
Prevents implementation from becoming the de facto specification for non-trivial work by insisting on a written, scoped specification before planning and execution. It reduces scope drift, unclear acceptance criteria, and accidental policy decisions encoded in code rather than documents.
Use the spec-driven skill to write a concise product or design spec that states the problem, goals, non-goals, acceptance criteria, and the minimal solution sketch.
High-intent search queries and answers about installing and using this skill.
To prevent implementation becoming the de facto specification, you must insist on a written, scoped specification before planning and execution. This reduces scope drift, unclear acceptance criteria, and accidental policy decisions encoded in code.
A product spec or design doc should include the problem, goals, non-goals, acceptance criteria, and a minimal solution sketch. Declaring these explicitly ensures reviewers and implementers share a single source of truth.
Write acceptance criteria for API changes by applying a spec-driven sequence: explore, write or update the spec, align, plan, then implement. This gating sequence defines required steps and prevents premature implementation.
You need a design doc versus a product spec based on the change type. Spec hygiene recommends the minimal spec type required—product spec, design doc, or both—ensuring the document is executable by downstream planning agents.
Spec-driven planning works for multi-file workflows by guiding authors to declare explicit goals, non-goals, and acceptance criteria. This scope enforcement ensures reviewers and implementers share a single source of truth.
Feature development has accidental policy decisions encoded in code when implementation becomes the de facto specification. Insisting on a written specification before planning and execution prevents these accidental policy decisions.
buddypiaGenerate technical specifications and documentation from user stories and requirements.
warpdotdevPlan and execute feature implementations while keeping specs aligned with code changes.
ArvorCoGenerate a structured PRD with goals, user stories, and acceptance criteria.
ahmedemad3Generate dependency-aware tasks.md from plan.md and spec.md.
