landscape-survey
Skill0 starsChanged 55 days agoNo licenceView on GitHub
Run a structured open-source landscape survey before designing or rebuilding a complex system. Six phases: bracket, discover (video + oracle + grounding doc), workspace (scratch clone), anchor read (manual, 1-2 closest peers), parallel deep-reads (team-dispatched), synthesis (single-worker comparative RE). Produces per-repo AREs + one comparative-analysis RE + grounding-doc cross-ref appendix; hands off to SD update and SPC drafting. Use whenever the user says "landscape survey", "deep-read these repos", "what should we borrow from X", "research before we spec", "evaluate candidates before the rebuild", "comparative source analysis", "what's the state of the art for [domain]", or invokes /landscape-survey. Also fires when the user points the assistant at a candidate set (a list of repos / libraries / approaches) and asks for a build plan before the SPC. The skill is the structural answer to "we built the system on marketing-page understanding and only discovered the failure mode after shipping."
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- wfk-closeoutSkill
- wfk-create-noteSkill
- wfk-create-specSkill
- wfk-discoverSkill
- wfk-explainSkill
- wfk-git-safeSkill
- wfk-implementSkill
- wfk-learnSkill
- wfk-log-workSkill
- wfk-orientSkill
- wfk-parkSkill
- wfk-pickupSkill
- wfk-plan-specSkill
- wfk-projectSkill
- wfk-review-specSkill
- wfk-rollupSkill
- wfk-setupSkill
- create-planSkill
- create-specSkill
- plan-specSkill
- wfk-projectSkill
- wfk-rollupSkill
- apikeysSkill
- article-intelSkill
- auto-researchSkill
- best-practiceSkill
- bracketSkill
- closeoutSkill
- create-noteSkill
- discoverSkill
- distill-lessonsSkill
- dreamSkill
- end-daySkill
- explainSkill
- frontend-designSkill
- git-safeSkill
- grillSkill
- impeccableSkill
- implementSkill
- intakeSkill
- itermSkill
- learnSkill
- limitlessSkill
- log-workSkill
- oracle-askSkill
- oracle-createSkill
- oracle-researchSkill
- orientSkill
- parkSkill
- pickupSkill
- plan-specSkill
- prototypeSkill
- pr-reviewSkill
- qa-coordSkill
- recapSkill
- resolve-irSkill
- retroSkill
- review-specSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
7
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 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.
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.