wi

List, show, and upsert backlog work items with revision-based state commits.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ether-moon/agent-atelier --skill wi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wi
Source: https://github.com/ether-moon/agent-atelier/tree/main/plugins/agent-atelier/skills/wi
Command: npx skills add https://github.com/ether-moon/agent-atelier --skill wi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and tracking work items across the backlog helps teams coordinate scope, status, and dependencies without losing context. This skill enables listing items, viewing details, and creating or updating items in a structured, auditable flow.

Core Features & Use Cases

  • List all work items in the backlog to get a quick overview of status and ownership.
  • Show detailed information for a specific work item to assess progress, blockers, and dependencies.
  • Create new work items or upsert updates to existing items, with validation and deterministic state mutation to preserve consistency.
  • Support for dependencies, status transitions, and revision-based concurrency to prevent conflicting changes.

Quick Start

List all work items with the command /agent-atelier:wi list.

Frequently Asked Questions about wi

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

FAQPage Schema
How do I track work item dependencies and status changes in a backlog?

Track work item dependencies and status changes by upserting items in the backlog using a strict revision-based mutation flow. This validates inputs and applies deterministic writes to preserve consistency across status transitions and dependency updates.

What is the best way to list and inspect backlog items for planning?

The best way to inspect backlog items for planning is to list all work items for a quick overview of status and ownership, then show detailed information for a specific item to assess progress, blockers, and dependencies.

How does revision-based concurrency prevent conflicting work item updates?

Revision-based concurrency prevents conflicting work item updates by enforcing a strict mutation flow with input validation and deterministic state commits. This ensures only validated, sequential changes are written to the backlog.

Can I upsert new and existing work items without losing context?

Yes, you can upsert new and existing work items without losing context. The skill creates new items or updates existing ones using deterministic state mutation and validation to preserve consistency across the backlog.

Does this backlog tracking approach support handling dependencies and blockers?

Yes, this backlog tracking approach supports handling dependencies and blockers. You can show detailed information for a specific work item to assess progress and map dependencies, then upsert updates to resolve blockers.