technical-spec
This Claude Skill helps write system requirements using the EARS methodology. It converts natural language into structured requirements with five patterns: Ubiquitous, State Driven, Event Driven, Optional Feature, and Unwanted Behaviour. The skill includes examples, common mistakes to avoid, and saves output to markdown files.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install zph-dotfiles-technical-spec
Repository
Skill path: home/dot_config/claude/skills/technical-spec
This Claude Skill helps write system requirements using the EARS methodology. It converts natural language into structured requirements with five patterns: Ubiquitous, State Driven, Event Driven, Optional Feature, and Unwanted Behaviour. The skill includes examples, common mistakes to avoid, and saves output to markdown files.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Tech Writer.
Target audience: Documentation teams looking for install-ready agent workflows..
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: zph.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install technical-spec into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/zph/dotfiles before adding technical-spec to shared team environments
- Use technical-spec for documentation workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.