spec-driven-implementation

Create PRODUCT.md and TECH.md specs linked to Linear tickets.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aetherrigstudio-art/Primordial-viz --skill spec-driven-implementation-aetherrigstudio-art
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-implementation
Source: https://github.com/aetherrigstudio-art/Primordial-viz/tree/main/.claude/skills/spec-driven-implementation
Command: npx skills add https://github.com/aetherrigstudio-art/Primordial-viz --skill spec-driven-implementation-aetherrigstudio-art

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps mitigate implementation ambiguity and enhance product quality by adopting a spec-first workflow.

Core Features & Use Cases

  • Spec Creation: Facilitates the creation of PRODUCT.md and TECH.md to document user experience and technical details.
  • Ticket Linkage: Ensures alignment with Linear tickets, aiding in issue tracking and collaboration.
  • Spec Versioning: Maintains spec documents with code changes, ensuring they reflect the final product.

Quick Start

Use the spec-driven-implementation skill to create a spec for a new feature in your project.

Frequently Asked Questions about spec-driven-implementation

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

FAQPage Schema
How do I use a spec-first workflow for software feature planning?

A spec-first workflow structures software feature planning by creating detailed specification documents before coding. This approach uses PRODUCT.md and TECH.md files to document user experience and technical details, ensuring complete alignment across product and technical requirements.

How do I link feature specification documents to Linear tickets?

Linking specification documents to Linear tickets ensures continuous alignment between your written specs and issue tracking. The spec-first workflow connects your PRODUCT.md and TECH.md files directly to Linear tickets, aiding issue tracking and team collaboration throughout development.

What is the best way to maintain specification documents with code changes?

Maintaining specification documents with code changes requires active spec versioning to ensure files accurately reflect the final product. By updating your PRODUCT.md and TECH.md files alongside code commits, you prevent documentation drift and preserve implementation clarity over time.

Does a spec-first workflow require separate files for product and technical details?

A spec-first workflow typically separates product and technical details by creating a PRODUCT.md for user experience documentation and a TECH.md for technical specifics. This structured separation enhances product quality by reducing implementation ambiguity across distinct project dimensions.

What problem does specification management solve in software development?

Specification management solves the problem of implementation ambiguity in software development by enforcing a structured, spec-first workflow. Documenting features thoroughly before coding mitigates misalignment between product goals and technical execution, ultimately enhancing overall product quality.