translate-brief
Skill2 starsChanged 17 days agoMITView on GitHub
Translate a filled-in CooperativeAICoding brief (Markdown Project_brief.md or page brief, or a JSON endpoint/database-model/solution-spec form) into terse specs in the project root's AI workspace (ai-only/) — a Project Digest, a solution spec, or an item spec — where every line cites the answer it came from and every gap is an UNKNOWN. Use whenever the user hands over or points at a filled-in CooperativeAICoding form and wants it turned into instructions an AI can build from.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buildSkill
- debtSkill
- draftSkill
- emit-guardrailsSkill
- new-itemSkill
- pipelineSkill
- productSkill
- qaSkill
- translateSkill
- verifySkill
- create-pipelineSkill
- draft-briefSkill
- emit-guardrailsSkill
- buildSkill
- debtSkill
- draftSkill
- emit-guardrailsSkill
- new-itemSkill
- pipelineSkill
- productSkill
- qaSkill
- translateSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 6
Read ai-only/procedures/translate.md under the project root you are working in, and follow it exactly.
≈ “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
Read ai-only/procedures/translate.md under the project root you are working in,
and follow it exactly. In this repository the canonical copy is
template/ai-only/procedures/translate.md; a project created with
coperativeai init has it at
ai-only/procedures/translate.md.
The procedure is the instruction, and it lives there rather than here so that
an agent which is not Claude Code reads the same text from AGENTS.md instead of
a copy that has drifted. Do not add behaviour to this file: a rule that exists in
.claude/ and nowhere else is a rule only one model follows.
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.