How do I install the Define Tech Spec skill?

Run npx skillmds@latest add hardness1020/define-tech-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Define Tech Spec skill do?

Create tech specs with architecture for Stage C of the VibeFlow docs-first workflow It is listed under Productivity on SkillMD.

Is Define Tech Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Define Tech Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Define Tech Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Define Tech Spec?

hardness1020 (@hardness1020) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Define Tech Spec by hardness1020 — Agent Skill

Name: Define Tech Spec
Author: hardness1020

File contents

define-tech-spec

Create tech specs with architecture for Stage C of the VibeFlow docs-first workflow.

Purpose

This skill creates and validates Tech Spec documents for Stage C:

Define architecture and interfaces
Document data contracts and SLOs
Specify component inventory and topology

Workflow

Stage C: Specify
    │
    ├── Create/update Tech Specs
    ├── Define architecture and interfaces
    └── Document data contracts and SLOs

Usage

Create/Update Tech Spec

/define-tech-spec <spec-name>

Creates or updates docs/specs/spec-<name>.md.

Example:

/define-tech-spec api
/define-tech-spec llm

Document Requirements

Tech Spec (`docs/specs/spec-<name>.md`)

Required sections:

Header (version, status, PRD link, contract versions)
Overview & Goals
Architecture (topology diagram + component inventory)
Interfaces & Data Contracts
Data & Storage
Reliability & SLIs/SLOs
Security & Privacy
Evaluation Plan

Validation

scripts/validate_techspec.py — Validate tech spec

References

See assets/:

techspec-template.md — Tech spec template

Context7 Library Research

Follow the workflow in .claude/rules/context7-research.md to fetch current library documentation.

What to look for: API surfaces, configuration options, integration patterns, version constraints.

Where to incorporate findings:

Architecture — topology and component interactions with external dependencies
Interfaces & Data Contracts — exact types, parameters, and return values from library APIs
Reliability — known limitations, failure modes, and SLO implications

Manifest Update

After completing Stage C, update docs/workflow-state.yaml:

Set stage: C
Append to docs.specs[]: docs/specs/spec-<name>.md

Git Commit

After completing this stage, ask the user for permission before committing:

git add docs/specs/spec-<name>.md docs/workflow-state.yaml
git commit -m "feat(spec): define <name> tech spec (#ft-<ID>)"

Replace <name> and <ID> with actual values.

Auto-Advance

After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

---name: define-tech-specdescription: Create tech specs with architecture for Stage C of the VibeFlow docs-first workflow---# define-tech-specCreate tech specs with architecture for Stage C of the VibeFlow docs-first workflow.## PurposeThis skill creates and validates Tech Spec documents for Stage C:- Define architecture and interfaces- Document data contracts and SLOs- Specify component inventory and topology## Workflow```Stage C: Specify │ ├── Create/update Tech Specs ├── Define architecture and interfaces └── Document data contracts and SLOs```## Usage### Create/Update Tech Spec```/define-tech-spec <spec-name>```Creates or updates `docs/specs/spec-<name>.md`.Example:```/define-tech-spec api/define-tech-spec llm```## Document Requirements### Tech Spec (`docs/specs/spec-<name>.md`)Required sections:- Header (version, status, PRD link, contract versions)- Overview & Goals- Architecture (topology diagram + component inventory)- Interfaces & Data Contracts- Data & Storage- Reliability & SLIs/SLOs- Security & Privacy- Evaluation Plan## Validation- `scripts/validate_techspec.py` — Validate tech spec## ReferencesSee `assets/`:- `techspec-template.md` — Tech spec template## Context7 Library ResearchFollow the workflow in `.claude/rules/context7-research.md` to fetch current library documentation.**What to look for:** API surfaces, configuration options, integration patterns, version constraints.**Where to incorporate findings:**- **Architecture** — topology and component interactions with external dependencies- **Interfaces & Data Contracts** — exact types, parameters, and return values from library APIs- **Reliability** — known limitations, failure modes, and SLO implications## Manifest UpdateAfter completing Stage C, update `docs/workflow-state.yaml`:- Set `stage: C`- Append to `docs.specs[]`: `docs/specs/spec-<name>.md`## Git CommitAfter completing this stage, ask the user for permission before committing:```bashgit add docs/specs/spec-<name>.md docs/workflow-state.yamlgit commit -m "feat(spec): define <name> tech spec (#ft-<ID>)"```Replace `<name>` and `<ID>` with actual values.## Auto-AdvanceAfter the commit is complete, directly run `/manage-work advance <ID>` to advance to the next stage.

Frequently asked questions

Define Tech Spec