spec-artifacts
Skill2 starsChanged 4 months agoMITView on GitHub
Use when a task needs a specific specification, decision, contract, release note, or handoff format.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-brief-directionSkill
- ui-polishSkill
- legacy-contractsSkill
- natural-writing-humanizationSkill
- project-memorySkill
- project-notesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Keep intended requirements distinct from current implementation.
- Very specific: line 12
Read references/formats.md for the selected artifact's fields.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Specification Artifacts
Produce only the requested artifact. Reuse the project's format and existing evidence; do not require a planning ceremony, fixed reading chain, or all artifact types.
Keep intended requirements distinct from current implementation. Identify the relevant repository or registered workspace members and the existing record destination; shared records do not authorize code or Git operations across members. Preserve local-only rules and user approval conditions.
Read references/formats.md for the selected artifact's fields. Preserve public API, data, version, and migration constraints when relevant. Record only verification actually performed. Detailed domain examples are optional in the repository reference library, not mandatory prerequisites.
For a long independent artifact, an optional delegated DRAFT must use bounded evidence and short relevant history. The parent reviews protected facts and unknowns before adoption; ordinary artifacts stay in the main task.
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.