(177665) Add ls command

This commit is contained in:
2026-05-14 21:37:11 +02:00
parent 17a02b906e
commit fd216b056c
4 changed files with 343 additions and 10 deletions
+46 -10
View File
@@ -4,8 +4,8 @@ name: worklane_kanban
version: 1.0.0
description: >
Creates Kanban-style tickets in Worklane using the `worklane add` CLI command.
Supports title, description, acceptance criteria, implementation plan, tags,
due date, and owner assignment.
Supports listing tickets with `worklane ls`. Both commands support title, description,
acceptance criteria, implementation plan, tags, due date, owner assignment, and status filtering.
rendering:
strategy: cli_args
join_arrays_with: ","
@@ -21,45 +21,49 @@ parameters:
type: string
required: true
cli_flag: "--title"
description:
type: string
required: false
cli_flag: "--description"
acceptance:
type: array
required: false
description: "List of acceptance criteria"
cli_flag: "--acceptance"
format: csv
plan:
type: array
required: false
description: "Step-by-step implementation plan"
cli_flag: "--plan"
format: csv
tags:
type: array
required: false
cli_flag: "--tags"
format: csv
due:
type: string
required: false
description: "Due date in YYYY-MM-DD format"
cli_flag: "--due"
owner:
type: string
required: false
cli_flag: "--owner"
---
command: worklane ls
parameters:
status:
type: string
required: false
description: "Filter by status (backlog, committed, reviewing, done)"
cli_flag: "--status"
```
Example:
Example adding a ticket:
```yaml
input:
title: "Implement login API"
@@ -81,7 +85,22 @@ output: >
--plan "Create auth controller,Add JWT middleware,Write tests"
--tags "backend,auth"
--due "2026-06-01"
--owner "alice"
--owner "alice"
```
Example listing tickets:
```yaml
input:
status: "backlog"
output: >
worklane ls --status backlog
```
Example listing all tickets (no filter):
```yaml
input: {}
output: >
worklane ls
```
## Agent Guidance (IMPORTANT — read before generating tickets)
@@ -143,3 +162,20 @@ When creating a Worklane ticket, the agent MUST:
* Do not repeat information across fields
* Ensure consistency between description, acceptance criteria, and plan
* If unsure, choose simpler and more testable phrasing
## Using `worklane ls`
The `worklane ls` command lists tickets. Use it to check the state of tickets:
* `worklane ls` — lists all tickets grouped by status without filtering
* `worklane ls --status <STATUS>` — filters tickets by status
Valid statuses: `backlog`, `committed`, `reviewing`, `done`
### Usage patterns
When checking ticket status or filtering work, use `worklane ls` rather than reading from file paths directly. This ensures consistent access to ticket data.
Example patterns:
* Check backlog items: `worklane ls --status backlog`
* View all tickets: `worklane ls`