understand-project
Skill66 starsChanged 56 days agoMITView on GitHub
Inspect the current product architecture, dependencies, and validation loops before planning or implementing a requested change.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Akylas/oss-weathertheir own version, first seen Oct 8, 2026
- Akylas/OSS-DocumentScannertheir own version, first seen Oct 8, 2026
- hamburger-os/PraxFlowtheir own version, first seen Sep 2, 2026
- Omerfaruk-aydn/Agent_OStheir own version, first seen Jul 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Akylas/OSS-DocumentScanner★ 2.6ksame name
- Akylas/oss-weather★ 478same name
- hamburger-os/PraxFlow★ 1same name
- Omerfaruk-aydn/Agent_OS★ 1same name
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 repository7 other files it gives its agents.
- kanban-workflowSkill
- plan-kanban-tasksSkill
- ralph-loopSkill
- kanban-workflowSkill
- plan-kanban-tasksSkill
- ralph-loopSkill
- understand-projectSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read AGENTS.md/CLAUDE.md, repository status, relevant source, tests, and existing product documentation in the integration or assigned …
- Very specific: line 11
Read related Kanban tasks and durable specs through the canonical metadata controller.
- Very specific: line 14
If the user requested planning, hand the findings to plan-kanban-tasks.
- Distinctive: line 15
Write a durable spec only when requested or materially useful, and route it to a controller-admitted location.
≈ “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
Understand the project
- Read
AGENTS.md/CLAUDE.md, repository status, relevant source, tests, and existing product documentation in the integration or assigned feature worktree. - Read related Kanban tasks and durable specs through the canonical metadata controller. Do not assume
.juno_task/plan.mdexists and do not materialize controller-private metadata in a product worktree. - Trace only the dependencies and runtime paths needed for the requested goal. Use bounded parallel investigation when independent questions justify it.
- Report current behavior, sources of truth, affected components, risks, unknowns, and the smallest useful validation loop.
- If the user requested planning, hand the findings to
plan-kanban-tasks. If implementation was requested, work only in the task worktree returned byyy task start TASK_ID. - Write a durable spec only when requested or materially useful, and route it to a controller-admitted location. Do not update root instructions with transient status.
Invocation contract
The structured views below intentionally alias parts of the complete request; they are not additional user arguments.
Main task
$1
Constraints and context
$2
Complete raw request
$ARGUMENTS
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.

