How does this skill use existing documentation?

The skill reads your project's high-level architecture files to extract purpose, boundaries, and dependencies, ensuring the new spec remains consistent with the broader system design.

Do I need to know every detail before starting?

No. The skill includes an interrogation phase that asks targeted questions about behavior and edge cases to help you define requirements you might have initially overlooked.

What format is the final specification?

It generates a structured Markdown file saved to a local /specs directory, featuring tables for data models, Mermaid code for diagrams, and numbered requirements.

Does it support testing criteria?

Yes, it specifically enforces a checklist that includes Given/When/Then acceptance criteria for every functional requirement to facilitate test-driven development.

Component Specification Generator

Name: Component Specification Generator
Author: pruett

bypruett

•

学習とドキュメンテーション

Generates detailed technical specifications by extracting and refining requirements from high-level architecture documents.

This skill bridges the gap between high-level system overviews and low-level implementation by creating thorough, standalone component specifications. It parses existing architectural documentation to establish context, then uses a systematic interrogation process to uncover missing details regarding interfaces, failure modes, and performance metrics. The result is a standardized Markdown specification featuring Mermaid diagrams, numbered requirements, and Given/When/Then acceptance criteria, ensuring developers have everything they need to begin implementation with confidence.

主な機能

018 GitHub stars

02Automated Mermaid diagram generation for system context and sequences

03Traceable requirement numbering for functional and non-functional specs

04Contextual extraction from existing architecture and design documents

05Standardized templates with Given/When/Then acceptance criteria

06Guided interrogation workflow to identify edge cases and failure modes

ユースケース

01Standardizing project documentation for clear developer handoffs and onboarding

02Drilling down from a high-level ARCHITECTURE.md into a specific microservice requirement

03Defining rigorous API schemas and validation criteria for a new system module

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add pruett/dotfiles component-spec

For use in Claude.ai and ChatGPT

Download Skill