spec

Automate specification workflows from idea to ADRs with structured outputs.

Updated Feb 27, 2025
One-click install
npx skills add https://github.com/tuanemuy/dotfiles --skill spec-tuanemuy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/spec
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill spec-tuanemuy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams struggle to convert vague ideas into concrete, implementable specifications and design artifacts, leading to miscommunication and rework.

Core Features & Use Cases

  • End-to-end specification workflow: from initial idea to ADRs, including scenario, page design, and domain considerations.
  • Structured outputs and traceability: generates and organizes spec/index.md, spec/scenario/index.md, spec/pages/index.md, and spec/adr/ records.
  • Review-driven process: enforces phase-based reviews and ADR documentation to ensure quality and clarity.

Quick Start

Review spec/idea.md, identify gaps, and generate the initial spec index to start Phase 0.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn vague product ideas into implementable specifications?

Generating end-to-end specifications requires an automated workflow that processes initial ideas through phase-based reviews. It outputs structured artifacts including scenario designs, page layouts, and architecture decision records for product teams.

What is the best way to document architecture decision records during product design?

Documenting architecture decision records effectively requires integrating them into an end-to-end specification workflow. This approach enforces phase-based reviews to generate structured ADR artifacts alongside scenario and page designs.

How does a phase-based specification workflow function from ideation to technical planning?

A phase-based specification workflow operates by guiding product teams from Phase 0 through Phase 3. It automates ideation, scenario design, page layout, and domain-oriented technical planning, producing structured markdown outputs for review readiness.

Do I need reference materials to generate structured design and scenario documentation?

Yes, clear inputs including a spec idea and reference materials are required to generate structured documentation. These references help identify gaps and produce organized outputs like spec/scenario/index.md and spec/pages/index.md.

Can I use this specification workflow for domain-oriented technical planning?

Yes, this specification workflow supports domain-oriented technical planning. It applies across ideation, scenario design, and page layout, producing architecture decision records to guide implementation phases and ensure traceability.

Why do teams struggle with converting ideas into concrete specifications?

Teams struggle with converting ideas into concrete specifications due to miscommunication and rework from unstructured processes. An end-to-end specification workflow solves this by enforcing phase-based reviews and generating structured, traceable design artifacts.