technical-spec
Skill8 starsChanged 43 days agoNo licenceView on GitHub
Produce the technical-specs/ document set (numbered NN-topic.md files plus _index.md) from the groomed business docs. Grills the user on tech stack and tooling first (this is the architectural keystone the rest of the pipeline depends on), then writes overview, architecture, repo structure, tech stack, module definitions, data model, security, NFRs, auth, integrations, environment config, and ad-hoc trailing specs for areas that need special technical attention. Use when the user wants a technical specification, TSD, architecture/data-model doc, or asks to "write the technical specs".
5 other projects use a version of this.
Adopted by
Most recently taken up by
- snowfluke/tech-lead-skillsword for word, first seen Nov 8, 2026
- shinpr/ai-coding-project-boilerplatetheir own version, first seen Nov 8, 2026
- SkillMedev/product-manager-stacktheir own version, first seen Oct 20, 2026
- Douglasst102/AgentSkillstheir own version, first seen Sep 28, 2026
- nandanosql/all_in_one_pm_skillstheir own version, first seen Feb 28, 2026
Other versions5 projects use a version of this.
Word for word · 1
- snowfluke/tech-lead-skills★ 8100% same
Edited · 0
None found.
Wrote their own version · 4
- shinpr/ai-coding-project-boilerplate★ 236same name
- Douglasst102/AgentSkills★ 4same name
- nandanosql/all_in_one_pm_skills★ 1same name
- SkillMedev/product-manager-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- lead-reviewSkill
- product-discoverySkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- tech-lead-setupsSkill
- test-auditSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- troubleshootingSkill
- us-ac-formatterSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.