From virtual-team
Defines abstract interface for backlog operations: list, get, create items, track status/progress, generate IDs. Load before read/write ops; delegates to local/external implementations.
npx claudepluginhub ovargas/virtual-team --plugin virtual-teamThis skill uses the workspace's default tool permissions.
This skill defines the backlog operations that commands use. It does NOT define how they're implemented — that's the job of the active backlog implementation skill (`virtual-team:backlog-local`, `virtual-team:backlog-external`, etc.), selected by the `backlog:` field in `stack.md`.
Manages local project backlog in docs/backlog.md using bracket markers for ready [ ], doing [>], implemented [=], done [x] statuses. Supports list(filter), get(id), create(items), start(id), next_id(), feature progress.
Manages backlog items through grooming, planning, and closure using GitHub Issues, Projects, Milestones. Interactive browser, auto-mode, resolve/close with evidence, SAM integration.
Manages backlog items across GitHub Issues, Linear, and Beads backends via unified CREATE/LIST/UPDATE/COMPLETE operations. Configure task_management in .agents.yml for team workflows with dependencies.
Share bugs, ideas, or general feedback.
This skill defines the backlog operations that commands use. It does NOT define how they're implemented — that's the job of the active backlog implementation skill (virtual-team:backlog-local, virtual-team:backlog-external, etc.), selected by the backlog: field in stack.md.
Commands MUST reference operations from this interface, never format-specific details. A command says "call start(id)" — the implementation skill decides whether that means editing a markdown file or calling an API.
stack.md and find the backlog: field (default: local if not specified)skills/backlog-{value}/SKILL.mdIf the backlog: field is missing from stack.md, assume local.
| Status | Meaning | Transition From | Transition To |
|---|---|---|---|
| ready | Specced and ready for work | (created) | doing |
| doing | Currently in progress | ready | implemented, done |
| implemented | Code complete, pending PR (branch flow only) | doing | done |
| done | Shipped | doing, implemented | (terminal) |
Direct-to-main flow: When working on main/master/develop, doing transitions directly to done — skip implemented entirely. There's no PR step.
Branch flow: doing → implemented → done (via PR merge).
Return backlog items matching the filter criteria.
Filters:
status — one of: ready, doing, implemented, done, allfeature — feature ID (e.g., FEAT-005)service — service tag (e.g., be, fe)group — group number within a featureReturns: List of items, each with: id, title, status, feature, group, order, service, spec path.
Return a single backlog item with all metadata.
Parameters: id — story ID (e.g., S-003) or ticket ID (e.g., CTR-12)
Returns: Full item metadata: id, title, status, feature, group, order, service, spec path.
Count items per status for a specific feature.
Parameters: feature_id — e.g., FEAT-005
Returns: Counts per status: ready, doing, implemented, done, total.
Generate the next available story ID (e.g., S-016 if the highest existing is S-015).
Returns: Next sequential story ID string.
Add new items to the backlog in ready status.
Parameters: List of items, each with: id, title, feature, group, order, service, spec path.
Behavior:
/virtual-team:vt-feature during story breakdownMove an item from ready to doing.
Parameters:
id — story IDBehavior:
Mark an item as code-complete, pending PR. Only used in branch flow.
Parameters:
id — story IDBehavior:
Mark an item as done.
Parameters:
id — story IDreference — PR number (branch flow) or "completed on main" (direct flow)Behavior:
These operations are no-ops for the local backend. External backends use them to keep the external service in sync.
Update the item's status in the external service.
Called after: Every status change (start, mark_implemented, complete).
Create or update a feature-level entry in the external service with a link to the local spec.
Called after: /virtual-team:vt-feature creates a feature spec.
Create or update story-level entries in the external service for all stories in a feature.
Called after: /virtual-team:vt-feature story breakdown.
Retrieve comments/feedback from the external service for an item.
Called before: /virtual-team:vt-implement starts a story (to check for team feedback).
Retrieve the current priority ordering from the external service.
Called by: /virtual-team:vt-implement when picking the next item (external ordering overrides local ordering).
Always load the backlog skill before any backlog operation. Read stack.md → load matching implementation skill.
Use operation names, not format details. Say "call list(ready)", not "read docs/backlog.md and parse bracket markers."
Commit after write operations. The implementation skill produces file changes (for local) or API calls (for external). Either way, commit local file changes immediately after the operation.
Handle errors from the skill. If an operation fails (item not found, API error), report the error and stop — don't fall back to a different implementation.
Sync operations are optional. Only call push_/pull_ if the backlog implementation indicates it supports them (external backends). Local backend ignores them.