skills.rest
OniroHuaver
OniroHuaverCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-implementation

Create PRODUCT.md and TECH.md specifications before implementing substantial features.

30|4|Updated May 3, 2026
Search Tags:#feature development#software design#specification#implementation#workflows
One-click install
npx skills add https://github.com/OniroHuaver/openwarp --skill spec-driven-implementation-onirohuaver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-implementation
Source: https://github.com/OniroHuaver/openwarp/tree/main/.agents/skills/spec-driven-implementation
Command: npx skills add https://github.com/OniroHuaver/openwarp --skill spec-driven-implementation-onirohuaver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing substantial features by ensuring a spec-first workflow, reducing ambiguity, and facilitating review.

Core Features & Use Cases

  • Spec Creation: Supports the creation of PRODUCT.md and TECH.md files for product and technical specifications.
  • Workflow Guidance: Offers a structured process for feature development, including ticket creation, spec writing, implementation, and verification.
  • Use Case: Ideal for teams starting significant features, where a clear specification can improve implementation quality and reduce ambiguity.

Quick Start

Run the spec-driven-implementation skill to start a new feature with a spec-first approach.

Frequently Asked Questions about spec-driven-implementation

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

FAQPage Schema
How do I reduce ambiguity when starting substantial feature development?▼

A spec-first workflow reduces ambiguity by requiring written product and technical specifications before any implementation begins. Creating these documents upfront ensures architectural clarity and improves overall implementation quality for substantial features.

What is the best way to structure product and technical specifications for a new feature?▼

Structuring product and technical specifications is best achieved by creating dedicated `PRODUCT.md` and `TECH.md` files. Separating product requirements from technical design provides a clear, reviewable foundation that guides subsequent implementation steps.

How do I implement a spec-first workflow for feature development?▼

Implement a spec-first workflow by following a structured process that spans ticket creation, spec writing, implementation, and verification. This sequence guides feature development logically from initial product requirements through to final technical execution.

When do I need written specifications for software design?▼

Written specifications for software design are needed when starting significant features that carry product or architectural ambiguity. They are essential whenever detailed implementation plans are necessary to mitigate risk and facilitate technical review.

Does spec-driven implementation work for small feature updates?▼

Spec-driven implementation is designed for substantial features rather than small updates. It is specifically suitable for significant features where product or architectural ambiguity exists and detailed implementation plans are necessary to ensure quality.

Related Skills

Explore More Software Engineering Skills→
zig-whatwgzig-whatwg
11

WHATWG Specification Implementation Skill

Translate WHATWG specifications into Zig implementations with numbered spec references.

Official
Advanced
rishikanthcrishikanthc

executing-plans

Execute implementation plans in batches with dependency checks and checkpoint reports.

Community
Advanced
Luney-IndustriesLuney-Industries
4

ship-task

Merge GitHub pull requests and transition Linear or Jira tickets to Done.

Official
Advanced
HR-ARHR-AR
1

ux-designer

Audit HTML, CSS, and vanilla JavaScript interfaces for UX bugs.

Community
Advanced