From 657e405c1e8df128fe1e08e12498fbc0533d5742 Mon Sep 17 00:00:00 2001 From: InsightFactoryAPP Date: Thu, 10 Sep 2026 15:06:34 -0400 Subject: [PATCH] feat: add ledger-tasks-yylo skill Adds a skill for operating YYLO Ledger task management (create, list, search, get, mark, update, archive, dependencies, ready/order queues, merges, cold-archive packs) via the yy ledger / yylo-ledger CLI. docs/README.skills.md regenerated with npm run build. --- docs/README.skills.md | 1 + skills/ledger-tasks-yylo/SKILL.md | 187 ++++++++++++++++++++++++++++++ 2 files changed, 188 insertions(+) create mode 100644 skills/ledger-tasks-yylo/SKILL.md diff --git a/docs/README.skills.md b/docs/README.skills.md index 24473fa6f4..e323afeeab 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -255,6 +255,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to | [kotlin-springboot](../skills/kotlin-springboot/SKILL.md)
`gh skills install github/awesome-copilot kotlin-springboot` | Get best practices for developing applications with Spring Boot and Kotlin. | None | | [landing-page-conversion-audit](../skills/landing-page-conversion-audit/SKILL.md)
`gh skills install github/awesome-copilot landing-page-conversion-audit` | Audit a landing page, sales page or checkout page for conversion leaks and return a fix list ordered by expected revenue impact. Use when asked to review, critique or improve a landing page, sales page, opt-in page, product page or checkout flow, when conversion rate is low, when paid traffic is not converting, or when someone asks "why isn't this page converting" or wants a CRO / landing page review. | None | | [latchshot-page-capture](../skills/latchshot-page-capture/SKILL.md)
`gh skills install github/awesome-copilot latchshot-page-capture` | Use this skill when a user needs a screenshot, website thumbnail, full-page capture, or PDF of a public HTTP(S) webpage saved as a local artifact through Latchshot, including report, QA, archive, and social-preview workflows. Do not use it for private or authenticated pages, raw HTML, scraping or extraction, arbitrary browser actions, CAPTCHA or anti-bot bypass, or local-file capture. | `scripts/latchshot.mjs` | +| [ledger-tasks-yylo](../skills/ledger-tasks-yylo/SKILL.md)
`gh skills install github/awesome-copilot ledger-tasks-yylo` | Operate YYLO Ledger task management for repositories that use YYLO: create, list, search, get, mark, update, and archive tasks, manage blocked-by dependencies, ready and topologically ordered queues for parallel execution, multi-directory merges, and immutable cold-archive packs through the `yy ledger` or standalone `yylo-ledger` CLI. Use when the user mentions YYLO, YYLO Ledger, yy ledger, yylo-ledger, yy kanban, or Kanban tasks in a YYLO-based repository, or asks an agent to pick the next unblocked task or update task status. Do not use for Ledger wiki, workflow, or artifact Record operations, direct edits to Ledger storage, or non-YYLO Kanban boards. | None | | [legacy-circuit-mockups](../skills/legacy-circuit-mockups/SKILL.md)
`gh skills install github/awesome-copilot legacy-circuit-mockups` | Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires. | `references/28256-eeprom.md`
`references/555.md`
`references/6502.md`
`references/6522.md`
`references/6C62256.md`
`references/7400-series.md`
`references/assembly-compiler.md`
`references/assembly-language.md`
`references/basic-electronic-components.md`
`references/breadboard.md`
`references/common-breadboard-components.md`
`references/connecting-electronic-components.md`
`references/emulator-28256-eeprom.md`
`references/emulator-6502.md`
`references/emulator-6522.md`
`references/emulator-6C62256.md`
`references/emulator-lcd.md`
`references/lcd.md`
`references/minipro.md`
`references/t48eeprom-programmer.md` | | [linkedin-post-formatter](../skills/linkedin-post-formatter/SKILL.md)
`gh skills install github/awesome-copilot linkedin-post-formatter` | Format and draft compelling LinkedIn posts using Unicode bold/italic styling, visual separators, structured sections, and engagement-optimized patterns. USE FOR: draft LinkedIn post, format text for LinkedIn, create social media post, write thought leadership post, convert content to LinkedIn format, LinkedIn carousel text, Unicode bold italic formatting. | `references/unicode-charmap.md` | | [lsp-setup](../skills/lsp-setup/SKILL.md)
`gh skills install github/awesome-copilot lsp-setup` | Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for Copilot CLI. Detects the OS, installs the right server, and generates the JSON configuration (user-level or repo-level). Use when you need deeper code understanding and no LSP server is configured, or when the user asks to set up, install, or configure an LSP server. | `references/lsp-servers.md` | diff --git a/skills/ledger-tasks-yylo/SKILL.md b/skills/ledger-tasks-yylo/SKILL.md new file mode 100644 index 0000000000..55a6c3e163 --- /dev/null +++ b/skills/ledger-tasks-yylo/SKILL.md @@ -0,0 +1,187 @@ +--- +name: ledger-tasks-yylo +description: 'Operate YYLO Ledger task management for repositories that use YYLO: create, list, search, get, mark, update, and archive tasks, manage blocked-by dependencies, ready and topologically ordered queues for parallel execution, multi-directory merges, and immutable cold-archive packs through the `yy ledger` or standalone `yylo-ledger` CLI. Use when the user mentions YYLO, YYLO Ledger, yy ledger, yylo-ledger, yy kanban, or Kanban tasks in a YYLO-based repository, or asks an agent to pick the next unblocked task or update task status. Do not use for Ledger wiki, workflow, or artifact Record operations, direct edits to Ledger storage, or non-YYLO Kanban boards.' +--- + +## YYLO Ledger CLI Reference + +Use `yy ledger` for all commands. YYLO 0.2.2 supports the exact `yylo-ledger 0.2.0` task CLI. `yy kanban` is a labelled compatibility alias for the same controller-routed task runtime. + +### Prerequisites + +This skill drives the YYLO Ledger task CLI. In a full YYLO workspace the commands run through +`yy ledger` (install the orchestrator with `npm install --global '@yylo/cli@latest'`; Node.js +20.10 or newer, npm, and Git are required). In a standalone Ledger project the same task surface +is provided by the separately installed `yylo-ledger` CLI. Source and documentation: + · · +. + +### Supported task contract + +- The public Ledger 0.2.0 surface is task-oriented: create, get, update, mark, archive, list/search, dependencies, ordering, history, doctor, compatibility, conversion, rollback, and cold archive operations. +- Do not advertise `record`, `wiki`, `workflow`, or `artifact` namespaces unless the installed `yy ledger --help` explicitly provides them in a future supported release. +- Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits. +- Normal discovery is hot-only unless an explicit cold-archive command is used. + +### Opt-in cross-project routing + +Cross-project access is disabled by default. The source `.juno_task/config.json` must set `kanbanRegistry.enabled: true` and explicitly list `allowedProjects`; environment overrides are `YYLO_LEDGER_REGISTRY_ENABLED` and `YYLO_LEDGER_REGISTRY_ALLOWED_PROJECTS`. Register with `yy ledger project add ALIAS --path /absolute/project`, then route any command with `--project ALIAS`. The destination wrapper/runtime remains authoritative, and routing failures never fall back to the source board. + +### Legacy Task compatibility commands + +**CREATE** — Add a new task +```bash +yy ledger create "Task description here" --status backlog --tags feature,backend +``` +Options: `--status` (backlog|todo|in_progress|done), `--tags` (comma/space-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs) + +**LIST** — Browse tasks with summary stats +```bash +yy ledger list --limit 5 --sort asc +yy ledger list --status todo --sort asc +yy ledger list --status todo,in_progress --limit 10 +``` + +**SEARCH** — Find tasks by criteria +```bash +yy ledger search --status todo --tag backend --limit 10 +yy ledger search --body "OAuth" --open +yy ledger search --commit abc123 +``` +Filters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags) + +**GET** — Full task details (including dependency info and related task details) +```bash +yy ledger get TASK_ID +``` + +**MARK** — Update status with required response message +```bash +yy ledger mark in_progress --id TASK_ID --response "Starting work on this" +yy ledger mark done --id TASK_ID --response "Completed: implemented X, tested Y" --commit abc123def +yy ledger mark todo --id TASK_ID --response "Reopening: found regression" +``` +Required: `--id` and `--response`. Optional: `--commit` (recommended for done). + +**UPDATE** — Modify task fields +```bash +yy ledger update TASK_ID --status todo --tags backend,urgent +yy ledger update TASK_ID --commit abc123def +yy ledger update TASK_ID --response "Additional context" +``` + +**ARCHIVE** — Soft delete (preserves data, sets status to archive) +```bash +yy ledger archive TASK_ID +``` + +### Immutable cold archive packs + +Normal `list`, `search`, `ready`, and `order` are deliberately hot-only. Exact `get TASK_ID` transparently resolves a hot task or a read-only archived task; use `history TASK_ID` explicitly for its ledger. Discover cold tasks only with bounded, projected `archive-search` output: + +```bash +yy ledger archive-search --tag backend --before 2026-01-01 --limit 20 --projection metadata +``` + +Before archive maintenance, preflight the installed version/help and obtain explicit owner authorization. The repository and index must be clean, and reports must be durable new paths outside the repository: + +```bash +yy ledger --version +yy ledger archive-pack plan --status done,archive --older-than 90d --max-tasks 1000 --target-bytes 26214400 --hard-max-bytes 47185920 --report /external/receipts/archive-plan.json +# Independently inspect selected IDs, revisions, source HEAD, policy, and plan hash. +yy ledger archive-pack create --plan /external/receipts/archive-plan.json --report /external/receipts/archive-create.json +yy ledger archive-pack doctor +yy ledger doctor +``` + +A stale plan or selected-task/worktree conflict must fail closed: discard the plan, resolve the conflict, and plan again. Never automate archival, edit/append packs or manifests, restore/reopen an archived ID, use force/lossy controls, or enumerate archive files directly. Create follow-up work as a new hot task related to the archived ID. Production archival, push/deploy, and post-deploy E2E each require separate authorization; agents must not infer it from implementation approval. + +### Dependency Management + +**DEPS** — View, add, or remove task dependencies +```bash +# View dependency info (blockers, dependents, priority score) +yy ledger deps TASK_ID + +# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done) +yy ledger deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2 + +# Remove a blocker +yy ledger deps remove --id TASK_ID --blocked-by BLOCKER1 +``` +Cycle detection prevents circular dependencies automatically. + +**READY** — Tasks with all blockers satisfied (safe to work on) +```bash +yy ledger ready +yy ledger ready --tag backend --limit 5 +``` +Returns tasks where status is backlog/todo/in_progress AND all `blocked_by` tasks are done/archive. + +**ORDER** — Topological sort of open tasks respecting dependencies +```bash +yy ledger order +yy ledger order --scores +``` +Use for determining safe parallel execution order. + +### Body Markup for Inline Dependencies + +Declare dependencies and relations directly in task body text: + +``` +[blocked_by]TASK_ID[/blocked_by] — This task is blocked by TASK_ID +[blocked_by]ID1, ID2[/blocked_by] — Blocked by multiple tasks +[task_id]RELATED_ID[/task_id] — Reference a related task +[task_id]ID1 ID2[/task_id] — Multiple related tasks +``` + +These are parsed automatically when the task is created/updated. + +### Merge (Multi-Directory Consolidation) + +When tasks get scattered across subdirectories: +```bash +# First produce and review a deterministic plan +yy ledger merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task \ + --dry-run --plan-file /external/ledger-merge-plan.json + +# Apply only that reviewed plan and retain its receipt +yy ledger merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task \ + --apply-plan /external/ledger-merge-plan.json \ + --receipt-file /external/ledger-merge-receipt.json +``` + +### Output Formats + +All commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table` +Add `--raw` for compact output. Add `-p` for pretty print. + +### Best Practices + +1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window +2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks) +3. **Always include `--response`** when using `mark` — document what you did and how you tested it +4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history +5. **Use `ready`** before starting work to find unblocked tasks +6. **Use `order --scores`** to plan parallel execution pipelines +7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others +8. **Use `[task_id]` markup** in task body to cross-reference related tasks +9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info +10. **Concurrent features are supported** — start each selected task with `yy task start TASK_ID`; each gets a dedicated product worktree, while `yy merge` serializes only target updates + +### Canonical Controller Routing + +YYLO Ledger mutation resolves the controller in this order: explicit `JUNO_TASK_ROOT`, repository-local registration, then the current project root. Diagnose before orchestration with `.juno_task/scripts/controller_resolver.py --cwd "$PWD" --operation kanban`. The resolver may bootstrap or idempotently confirm a registration, but changing an existing controller requires `yy migrate registration plan` followed by a separately authorized apply. Explicit/registered path or branch errors fail closed—YYLO Ledger never switches Git branches or falls back silently. + +Run YYLO Ledger and workflows from the controller. A task checkout may implement/test but routes task/session writes to that controller. An integration-owner checkout stays clean and refuses Kanban/orchestration/session writes in strict mode; launch from the controller and pass the product checkout separately as `TASK_ROOT`. + +### Environment Variables + +- `JUNO_TASK_ROOT` — Explicit canonical controller/task-storage root (not the product `TASK_ROOT`) +- `JUNO_CONTROLLER_BRANCH` — Expected controller branch for environment-based routing +- `JUNO_WORKSPACE_ROLE` — `controller`, `task`, or `integration-owner` +- `JUNO_WORKSPACE_ENFORCEMENT` — `off`, `warn`, or `strict` +- `JUNO_DEBUG=true` — Show diagnostic messages +- `JUNO_VERBOSE=true` — Show informational messages +- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)