specify
Skill2 starsChanged 6 months agoNo licenceView on GitHub
Substantial-path specification skill. Invokes product-planner + architect IN PARALLEL, merges into unified SPEC.md. By default AUTO-CONTINUES to /skill:plan (no gate). Only blocks for user approval when SKYNEX_HITL=strict.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
- ZaxbyHub/opencode-swarmtheir own version, first seen Oct 30, 2026
- jantichy/claudetheir own version, first seen Oct 27, 2026
- totalfrank/skillstheir own version, first seen Oct 27, 2026
- danielcherubini/skillstheir own version, first seen Oct 25, 2026
- genkovich/sddtheir own version, first seen Oct 25, 2026
Used with
Projects with it also use discovery, spec-review and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
robzolkosSkilldiscovery
Quick user-centric interview to capture requirements from a time-poor stakeholder.
Also in 3 projects that use this
MicrosoftSkillspec-review
Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.
Also in 3 projects that use this
- MicrosoftSkill
init
Also in 5 projects that use this
MetaSkillroadmap
Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.
Also in 3 projects that use this
sahinSkillexecute
Also in 3 projects that use this
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 5 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- zaxbysauce/opencode-swarm★ 519same name
- ZaxbyHub/opencode-swarm★ 518same name
- genkovich/sdd★ 187same name
- team-attention/hoyeon★ 173same name
- ArvorCo/Relentless★ 98same name
- jantichy/claude★ 45same name
- mehrad-dm/mastermind★ 23same name
- agent-ix/quoin★ 20same name
- danielcherubini/skills★ 14same name
- stormlightlabs/thunderus★ 4same name
19 more not listed
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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-reviewSkill
- archive-specSkill
- branch-prSkill
- buildSkill
- chained-prSkill
- cognitive-doc-designSkill
- comment-writerSkill
- discoverSkill
- grill-meSkill
- onboardSkill
- planSkill
- prdSkill
- proposeSkill
- researchSkill
- securitySkill
- skynex-executeSkill
- skynex-researchSkill
- skynex-sddSkill
- skynex-taskSkill
- syncSkill
- tdd-disciplineSkill
- validateSkill
- verification-before-completionSkill
- work-unit-commitsSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
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 27 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.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.