ce-strategy
Skill82 starsChanged 3 months agoLicence not identifiedView on GitHub
Create or maintain STRATEGY.md - the product's target problem, approach, users, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also triggers when ce-ideate, ce-brainstorm, or ce-plan need upstream grounding and no strategy doc exists yet.
We split this skill into the rules it gives an agent
16 rules. 0 are common, 7 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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 6 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.
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- EveryInc/compound-engineering-plugin★ 26k10% same
- EveryInc/compounding-engineering-plugin★ 26k10% same
- EveryInc/every-marketplace★ 26k10% same
- kieranklaassen/compound-engineering-plugin★ 26k10% same
- MortuisVMain/ai-agent-superpowers★ 011% same
- Pdbjork/hermosskills-site★ 095% same
Wrote their own version · 0
None found.
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.
Used alongsideProjects with it also use ce-explain, ce-handoff and 10 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.
EveryIncSkillce-explain
Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.
Also in 5 projects that use this
EveryIncSkillce-handoff
Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.
Also in 5 projects that use this
aspi6246Skillwtf
Re-explain the previous response in plain language when the user did not follow it. Use this skill when the user types "wtf", "wtf?", "huh?", "in English?", "say that simpler", "I don't follow", "you lost me", "explain that again but simpler", "eli5 that", or any short reaction signalling the last answer was too long, too dense, or too jargon-heavy. Rephrases what was already said in ASD-STE100 Simplified Technical English — it does not answer a new question or redo the work.
Also in 4 projects that use this
- +9 more from EveryInc
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- home/CLAUDE.mdCLAUDE.md
- ai-elementsSkill
- clerk-custom-uiSkill
- clerk-nextjs-patternsSkill
- clerk-orgsSkill
- clerk-setupSkill
- clerkSkill
- clerk-testingSkill
- clerk-webhooksSkill
- commitSkill
- debugSkill
- landSkill
- launch-appSkill
- linearSkill
- matrix-handoffSkill
- orchestrate-problem-prsSkill
- pullSkill
- pushSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- worktree-pr-monitorSkill
- ce-code-reviewSkill
- ce-compoundSkill
- ce-workSkill
- integration-nextjs-app-routerSkill
- preview-envSkill
- animateSkill
- animation-accessibilitySkill
- animation-performanceSkill
- animation-vocabularySkill
- matrix-app-builderSkill
- apple-designSkill
- matrix-app-ui-patternsSkill
- matrix-chat-importSkill
- css-animationsSkill
- matrix-debug-appSkill
- matrix-design-systemSkill
- matrix-dev-vpsSkill
- emil-design-engSkill
- matrix-integrationsSkill
- matrix-jev-email-triageSkill
- matrix-landing-designSkill
- matrix-osSkill
- matrix-personal-daily-briefSkill
- review-animationsSkill
- shadcnSkill
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.

