deep-plan
Skill2 starsChanged 8 months agoLicence not identifiedView on GitHub
Use when user needs to plan implementation of a designed system. Triggers: "plan the implementation", "create a project plan", "break this into sprints", "how do we implement this", "implementation roadmap".
16 other projects use a version of this.
Adopted by
Most recently taken up by
- ryanportfolio/HarnessFirmware.comtheir own version, first seen Nov 8, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- ryanportfolio/Harness-Firmwaretheir own version, first seen Nov 7, 2026
- ryanportfolio/Corewise.Academytheir own version, first seen Nov 1, 2026
- oguzsabi/deep-skillstheir own version, first seen Nov 1, 2026
- ryanportfolio/STKtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use addskill, apply-firmware 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.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
- ryanportfolioSkill
apply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- piercelamb/deep-plan★ 104same name
- baekenough/oh-my-customcode★ 42same name
- phj128/autoworker★ 18same name
- npow/claude-skills★ 4same name
- jasonmichaelbell78-creator/sonash-v0★ 2same name
- ryanportfolio/winuse-mcp★ 2same name
- abhijit-nexlytix/claude-skills★ 1same name
- oguzsabi/deep-skills★ 1same name
- ryanportfolio/Corewise.Academy★ 1same name
- ryanportfolio/Harness-Firmware★ 1same name
6 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 repository22 other files it gives its agents.
- deep-aggregateSkill
- deep-alignSkill
- deep-architectSkill
- deep-challengeSkill
- deep-changeSkill
- deep-complianceSkill
- deep-deploySkill
- deep-diagramSkill
- deep-documentSkill
- deep-exploreSkill
- deep-feasibilitySkill
- deep-governanceSkill
- deep-governSkill
- deep-implementSkill
- deep-monitoringSkill
- deep-orchestrationSkill
- deep-requirementsSkill
- deep-riskSkill
- deep-synthesisSkill
- deep-testSkill
- deep-ventureSkill
- deep-verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
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 15 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.