backlog

Edit backlog ledger rows while preserving collaborator status changes.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/vhqtvn/vh-solara --skill backlog-vhqtvn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/vhqtvn/vh-solara/tree/main/.opencode/skills/backlog
Command: npx skills add https://github.com/vhqtvn/vh-solara --skill backlog-vhqtvn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you update the shared backlog ledger without overwriting a collaborator's status changes, and it keeps deferred findings out of the backlog until they are ready to promote.

Core Features & Use Cases

  • Conflict-safe backlog edits: Re-read the ledger, edit only your own row, and keep backlog commits separate from code commits.
  • Conflict recovery: When a cas_conflict happens, re-read the new state and re-apply your change instead of blindly reverting the file.
  • DEFER and follow-up routing: Send DEFER, p2, and follow-up items to the holding area first, then promote them only when the trigger and definition of ready are satisfied.

Quick Start

Use the backlog skill to update the relevant task row in docs/planning/backlog.md while preserving collaborator edits and avoiding blind reverts.

Frequently Asked Questions about backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent backlog ledger conflicts when editing shared task statuses?

Prevent backlog ledger conflicts by re-reading the ledger before editing, modifying only your own row using stable IDs, and keeping backlog commits separate from code commits to preserve collaborator edits.

What is the best way to recover from a cas_conflict in a shared task ledger?

Recover from a cas_conflict by re-reading the new ledger state and re-applying your change, rather than blindly reverting the file and overwriting your collaborator's recent task-status updates.

How do I route deferred findings and p2 items in planning workflows?

Route DEFER, p2, and follow-up items to a holding area first, then promote them to the backlog only when their trigger and definition of ready conditions are fully satisfied.

Does backlog conflict resolution require separate commits for task tracking updates?

Yes, backlog conflict resolution requires keeping backlog commits separate from code commits, ensuring safe coordination and preventing accidental overwrites of collaborator task-status edits.

When should I not promote a deferred task into the backlog?

Do not promote a deferred task into the backlog when its trigger or definition of ready is unsatisfied, leaving it in the holding area until provenance-based promotion rules are fully met.