skills.rest
thomfilg
thomfilgCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Generate technical specifications from product briefs and codebase analysis.

Updated Feb 25, 2026
Search Tags:#code analysis#technical documentation#specification generation#product brief analysis#specification tool
One-click install
npx skills add https://github.com/thomfilg/ai-plugin-work --skill spec-thomfilg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/thomfilg/ai-plugin-work/tree/main/plugins/work/skills/spec
Command: npx skills add https://github.com/thomfilg/ai-plugin-work --skill spec-thomfilg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating technical specifications from product briefs and codebase analysis, reducing manual effort and ensuring comprehensive documentation.

Core Features & Use Cases

  • Technical Spec Generation: Automatically generates a technical specification based on codebase analysis and product briefs.
  • Customizable Output: Outputs specifications with architecture decisions, data model changes, API contracts, security considerations, and test scenarios.
  • Use Case: Generate a detailed spec for a software project by providing the ticket ID or folder name.

Quick Start

Generate a spec for a ticket with the ID 'PROJ-123' by running the command: /spec PROJ-123.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I generate a technical specification from a product brief and codebase?▼

You can generate a technical specification by running a command with a ticket ID or folder name, which analyzes the product brief and codebase to output detailed documentation covering architecture, data models, and API contracts.

What sections are included in an automated technical specification?▼

An automated technical specification includes architecture decisions, data model changes, API contracts, security considerations, and test scenarios derived from codebase analysis and product briefs.

Can I create documentation for an existing codebase without writing it manually?▼

Yes, you can create documentation for an existing codebase by providing the specific folder name, which automates the analysis process and generates a comprehensive technical specification reducing manual effort.

What is the best way to document API contracts and data model changes for a new feature?▼

The best way to document API contracts and data model changes is using automated specification generation, which extracts details from product briefs and codebase analysis to ensure comprehensive technical documentation.

Does automated specification generation work for software engineering workflows requiring test scenarios?▼

Yes, automated specification generation works for software engineering workflows by producing technical specifications that explicitly include test scenarios alongside security considerations and architecture decisions.

Related Skills

Explore More Software Engineering Skills→
ag3nt3154ag3nt3154
1

pms-init

Create raw and wiki folder structures with six wiki stub documents.

Community
Intermediate
tobieapbtobieapb
105

Interview Methodology Skill

Optimized for clarity and speed, discover the best-fit coffee bean for your personality and palate with our quick quiz — choose wisely, your next favorite awaits!

Community
Advanced
rotnovrotnov

changelog-automation

Generate changelog entries from commits and pull requests following Keep a Changelog.

Community
Intermediate
LFDT-NightstreamLFDT-Nightstream
29

de-slopify

Edit documentation prose to remove AI writing artifacts like emdash overuse.

Official
Intermediate