Overview

This skill provides local-first backlog management across multiple products with disciplined agent collaboration. It uses a thin wrapper that points to canonical documentation, ensuring teams share a single source of truth. Use the quick-start commands to validate your environment and refresh backlog views for different products and agents.

How This Skill Works

It works as an OpenCode Skill Adapter that delegates operations to the kano-backlog tool. The included commands demonstrate how to perform an environment check (doctor) and to refresh product/backlog views (view refresh) for a given product and agent. This setup keeps local backlog state coordinated with the canonical docs while supporting multi-product collaboration.

When to Use It

• When coordinating backlog across multiple products on a local-first setup
• When onboarding new agents to backlog collaboration discipline
• When you need to verify your environment before backlog operations
• When you must refresh backlog views to reflect latest work
• When operating in offline or unstable connectivity and need local backlog access

Quick Start

1. Step 1: Environment check: python skills/kano-agent-backlog-skill/scripts/kano-backlog doctor --format plain
2. Step 2: Refresh views: python skills/kano-agent-backlog-skill/scripts/kano-backlog view refresh --product kano-agent-backlog-skill --agent opencode
3. Step 3: Read canonical docs: skills/kano-agent-backlog-skill/SKILL.md

Best Practices

• Keep product-specific backlog views local and isolated
• Enforce a clear agent collaboration protocol
• Regularly run the doctor environment check
• Rely on the canonical documentation as the single source of truth
• Document backlog changes and sync points to avoid divergence

Example Use Cases

• A distributed development team manages backlogs for two products locally before syncing to a central source
• An onboarding session where new agents learn the backlog discipline using local views
• A hackathon where participants plan tasks locally and perform a backlog refresh for consistency
• A field team uses offline backlog planning with later synchronization to ensure shared priorities
• A release-prep session where the product backlog views are refreshed for the current agent

Frequently Asked Questions