Singam Tech Inc
- Updated June 16, 2026
- Singam-Tech-Inc/spec-generator
Spec Generator is a Claude Code plugin that automatically generates numbered API specification directories, task breakdowns, and git branches from natural-language descriptions.
About
The Singam Tech spec-generator marketplace plugin automates API specification files with numbered spec directories, intelligent subtask generation, and git branch integration. Commands like /stspec:c scaffold spec folders, taskfiles, and branches from a description, with optional custom Jekyll templates under .claude/spec-templates/. Reach for it when you want repeatable API specs and tasks before coding OAuth endpoints or similar features. The marketplace manifest is minimal; feature detail comes from this plugin README.
- /stspec:c with description creates SPEC-00001-style directories
- Git branch spec-NNNNN-slug with confirm-before-commit flow
- Custom templates in .claude/spec-templates/
- Jekyll YAML templates with Fibonacci story points
Singam Tech Inc by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add Singam-Tech-Inc/spec-generatorAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | June 16, 2026 |
|---|---|
| Repository | Singam-Tech-Inc/spec-generator ↗ |
How do you spin up consistent API specs, tasks, and git branches without manual folder numbering and copy-paste templates?
Creates auto-numbered SPEC-NNNNN API spec folders, AI-generated taskfiles, git branches, and optional custom Jekyll templates.
Who is it for?
Teams using Claude Code who want SPEC-NNNNN layouts and AI-generated subtasks before API implementation.
Skip if: Repos that do not use git or projects that reject spec-driven folder conventions entirely.
What you get
A spec/SPEC-NNNNN-slug/ tree with API spec files, taskfiles, and a matching git branch awaiting your commit confirmation.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
What numbering format is used?
Specs use SPEC-NNNNN with auto-increment and matching spec-NNNNN-slug git branches.
Where do custom templates live?
Place them in .claude/spec-templates/ as Jekyll-format markdown templates.
How is project root determined?
Read project_root from .claude/settings.json or search upward for a .git directory.