skills.rest
hardness1020
hardness1020COMMUNITY
Explore all skills by this author →
GitHub

define-tech-spec

Create and validate Stage C tech specs with architecture definitions and data contracts.

8|Updated Sep 22, 2025
Search Tags:#architecture#specification#validation#tech-spec#data-contracts#stage-c#docs-first
One-click install
npx skills add https://github.com/hardness1020/VibeFlow --skill define-tech-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define-tech-spec
Source: https://github.com/hardness1020/VibeFlow/tree/main/.claude/skills/define-tech-spec
Command: npx skills add https://github.com/hardness1020/VibeFlow --skill define-tech-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Tech teams often struggle to crystallize Stage C architecture and data contracts before implementation, leading to rework and miscommunication.

Core Features & Use Cases

  • Define architecture and interfaces for Stage C documents.
  • Document data contracts, SLIs/SLOs, security considerations, and evaluation plans.
  • Use the standard tech spec template to maintain consistency across specs (docs/specs/spec-<name>.md).

Quick Start

Run /define-tech-spec <spec-name> to create or update docs/specs/spec-<name>.md.

Frequently Asked Questions about define-tech-spec

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

FAQPage Schema
How do I define a Stage C tech spec with architecture and data contracts?▼

Use a standard tech spec template to define architecture, interfaces, data contracts, SLIs/SLOs, and security considerations in docs/specs/spec-<name>.md for disciplined documentation.

What sections are required in a Stage C architecture specification?▼

A Stage C architecture specification requires sections for architecture definitions, interfaces, data contracts, SLIs/SLOs, security considerations, and evaluation plans, ensuring complete technical alignment before implementation begins.

How do I validate a tech spec document for required headers and sections?▼

Validate a tech spec document by running a validation script that checks if docs/specs/spec-<name>.md follows the required header and sections defined in the tech spec template guide.

Can I use this tech spec template for workflows outside of Stage C?▼

This tech spec template applies specifically to Stage C workflows, focusing on crystallizing architecture and data contracts to prevent rework and miscommunication during those defined stages.

What is the best way to document data contracts and SLIs before implementation?▼

The best way to document data contracts and SLIs is using a docs-first approach with a standardized tech spec template, ensuring all interfaces and evaluation plans are validated before coding starts.

Why does defining architecture before implementation reduce rework?▼

Defining architecture before implementation reduces rework by crystallizing data contracts and technical interfaces early, preventing miscommunication and ensuring all teams align on the same architecture specifications.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
fiatkongenfiatkongen

dotnet-writing-plans

Generate structured implementation plans from feature specs for .NET backend tasks.

Community
Basic
dacydacy

tech-stack-skill

Enforce approved technology choices and log exceptions against the company tech catalog.

Community
Intermediate
atholaathola
326

makefile-dogfooder

Analyze Makefiles and generate missing demo, dogfood, and quick-run targets.

Community
Intermediate