skills.rest
friedbotstudio
friedbotstudioOFFICIAL
Explore all skills by this author →
GitHub

spec

Draft build-ready technical specifications with PlantUML diagrams and traceable acceptance criteria.

5|Updated Apr 29, 2026
Search Tags:#workflow#documentation#rollback#acceptance criteria#plantuml#technical spec#rollout
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill spec-friedbotstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/friedbotstudio/baseline --skill spec-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns intake materials into a build-ready technical specification so engineers can implement a change with clear scope, contracts, tests, and rollout guidance.

Core Features & Use Cases

  • Diagram-first planning: Produces C4, class, sequence, and dependency diagrams as the core design contract.
  • Traceable requirements: Links acceptance criteria, behavior sections, and test plans so the spec is actionable and reviewable.
  • Delivery guidance: Captures rollout, rollback, open questions, and alternatives for complex software work.
  • Use Case: A team has an intake, a BRD, and research notes for a feature; this Skill converts them into a structured spec in docs/specs/<slug>.md that another engineer can build from.

Quick Start

Use the spec skill to draft a technical spec from the intake and any supporting research for the current feature.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I draft a technical specification from intake artifacts and research notes?▼

To draft a technical specification, you convert intake materials like BRDs and research notes into a build-ready design document with traceable acceptance criteria, contracts, test plans, and rollout guidance. The output is a structured markdown file saved to docs/specs/.

How do I generate PlantUML diagrams for a software design document?▼

You generate PlantUML diagrams by applying a diagram-first planning approach to your software workflow changes. This produces C4, class, sequence, and dependency diagrams as the core design contract within your technical spec.

What should be included in a technical spec for rollback and rollout guidance?▼

A technical spec should include structured rollout and rollback sections alongside open questions and alternatives. This delivery guidance ensures engineers have actionable plans for complex software deployment and recovery scenarios.

Can I use acceptance criteria and test plans to make a technical specification reviewable?▼

Yes, you link acceptance criteria, behavior sections, and test plans together to make the technical specification actionable and reviewable. This traceability ensures every requirement maps directly to its corresponding test.

Does drafting a technical specification require self-approval before implementation?▼

No, drafting a technical specification explicitly prohibits self-approval to maintain quality. The spec requires an external approval flow where another engineer reviews the structured markdown before building from the design document.

What is the best way to structure workflow-driven software changes in a technical spec?▼

The best way to structure workflow-driven software changes is using structured markdown sections that capture diagrams, contracts, tests, and delivery guidance. This creates a build-ready design document another engineer can implement from.

Related Skills

Explore More Software Engineering Skills→
RangeyRoverRangeyRover
3

speckit.plan

Generate research documents, data models, and API contracts from feature specifications.

Community
Advanced
carterbscarterbs
4

implement-plan

Execute implementation plans phase by phase with automated verification at each milestone.

Community
Advanced
robtaylorrobtaylor
3

c4-diagrams

Model and visualize software architecture with C4 diagrams and PlantUML.

Community
Intermediate
AZANIRAZANIR
2

qa-spec-writer

Transform requirements into technical specifications with Gherkin acceptance criteria.

Community
Intermediate