Understand Project Yylo

Inspect the current product architecture, dependencies, and validation loops before planning or implementing a requested change.

1 stars 1 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add yylo-dev/yylo-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add yylo-dev/yylo-skills --skill understand-project-yylo
Manual install
git clone --depth 1 https://github.com/yylo-dev/yylo-skills.git /tmp/yylo-skills
mkdir -p ~/.claude/skills
cp -r /tmp/yylo-skills/skills/understand-project-yylo ~/.claude/skills/understand-project-yylo

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the 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-ledger-tasks-yylo`. If implementation was requested, work only in the task worktree returned by `yy task start TASK_ID`.
6. Write a durable operational spec only when requested or materially useful. Draft it externally, preflight the installed `yy ledger artifact` API, capture it as an immutable `report` Artifact Record with provenance/retention, and verify retrieval, digest, and history. If that API is unavailable, stop with the external draft intact; never fall back to product `docs/`, task bodies/responses, new `.juno_task/specs`, or direct controller-store edits. Product `docs/` remains reserved for documentation shipped with the product. Do not update root instructions with transient status.

## Retrieve context without guessing types
Read the full skill on GitHub

Details

Skill name
understand-project-yylo
Path
skills/understand-project-yylo/SKILL.md
License
MIT
Repo updated
17 October 2026

FAQ

What does the Understand Project Yylo skill do?

Inspect the current product architecture, dependencies, and validation loops before planning or implementing a requested change.

How do I install the Understand Project Yylo skill?

Claude Code plugin: /plugin marketplace add yylo-dev/yylo-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Understand Project Yylo popular?

It lives in yylo-dev/yylo-skills, which has 1 GitHub stars and 1 forks, and is included in 1 curated skill list.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.