Plan Ledger Tasks Yylo

Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.

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 plan-ledger-tasks-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/plan-ledger-tasks-yylo ~/.claude/skills/plan-ledger-tasks-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

# Plan Kanban work

1. Read the project instructions and relevant product code from the integration or feature worktree. Read existing task/spec metadata through the canonical controller; do not assume `.juno_task/plan.md` exists.
2. Produce one concise PDR covering the goal, current behavior, scope, exclusions, risks, dependencies, acceptance criteria, and focused tests. Draft it in a fresh external file; do not place it in the product tree or a task body.
3. Preflight `yy ledger --help` and `yy ledger artifact --help`. Capture the PDR as a local immutable `report` Artifact Record with task/request provenance, then verify its ID, digest, size, retention, retrieval, and history. If the artifact API is unavailable, stop with the external draft intact and request an upgrade; never fall back to product `docs/`, task bodies/responses, new `.juno_task/specs`, or direct store edits.
4. Split only when pieces can be implemented and validated independently. Concurrent tasks must have explicit path ownership and dependencies.
5. Create tasks through routed `yy ledger` commands. Put concise durable requirements and acceptance criteria in each task body, record the PDR artifact ID in supported task fields/provenance, and relate follow-ups instead of reopening archived IDs.
6. Product documentation is only documentation shipped with the product. Never create controller-private tasks, ledger, state, artifacts, objects, specs, or receipts inside a product or feature worktree.
Read the full skill on GitHub

Details

Skill name
plan-ledger-tasks-yylo
Path
skills/plan-ledger-tasks-yylo/SKILL.md
License
MIT
Repo updated
17 October 2026

FAQ

What does the Plan Ledger Tasks Yylo skill do?

Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.

How do I install the Plan Ledger Tasks 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 Plan Ledger Tasks 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.