agentleFS
yylo-devyylo-dev/yylo/.agents/skills/understand-project/SKILL.md

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

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
  1. Distinctive:

    Read AGENTS.md/CLAUDE.md, repository status, relevant source, tests, and existing product documentation in the integration or assigned …

    line 10
  2. Very specific:

    Read related Kanban tasks and durable specs through the canonical metadata controller.

    line 11
  3. Very specific:

    If the user requested planning, hand the findings to plan-kanban-tasks.

    line 14
  4. Distinctive:

    Write a durable spec only when requested or materially useful, and route it to a controller-admitted location.

    line 15

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Understand the project

  1. Read AGENTS.md/CLAUDE.md, repository status, relevant source, tests, and existing product documentation in the integration or assigned feature worktree.
  2. Read related Kanban tasks and durable specs through the canonical metadata controller. Do not assume .juno_task/plan.md exists and do not materialize controller-private metadata in a product worktree.
  3. Trace only the dependencies and runtime paths needed for the requested goal. Use bounded parallel investigation when independent questions justify it.
  4. Report current behavior, sources of truth, affected components, risks, unknowns, and the smallest useful validation loop.
  5. If the user requested planning, hand the findings to plan-kanban-tasks. If implementation was requested, work only in the task worktree returned by yy task start TASK_ID.
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.