Adding triage skill to create tickets

nbd/.claude/skills/triage/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: triage
+description: triage issues
+---
+
+* Read @docs @src @tests @PLAN.md @README.md and @CLAUDE.md for context before starting.
+* Deeply understand each item before planning.
+* Create `nbd` tickets for each item including your plan, breaking the problem down into smaller tickets where it makes sense.
+* Include relevant source files, documentation, and context about each ticket so the work has the higest probability of success without additional context being required.
+* Do not implement any tickets.

nbd/triage-example.md

@@ -1,23 +0,0 @@
-Add the following tickets:
-
-Read @docs @src @tests @PLAN.md @README.md and @CLAUDE.md for context.
-
-* Add a `--filter` flag to `list`, `ready`, and `migrate` commands.
-    * This should accept `key=value` pairs for all metadata.
-    * Keys include: priority, type, status, title.
-    * Users can pass multiple key=value pairs.
-    * When passing different keys this is a logical AND reducing the results.
-    * When passing the same key with different values, this results in a logical OR expanding the results.
-    * Values should support globs,
-      * Example: `status=*` matches all status values
-      * Example: `--title=*command*` matches all tickets with 'command' in the title
-
-* By default do not include `done` tasks in `nbd list`. Require `--filter status=*` or `--filter status=done`
-
-* Add a new `next` subcommand which chooses the highest priority ticket which is ready to be worked on.
-    * This should support the `--filter` flag.
-
-Deeply understand each item before planning.
-Create `nbd` tickets for each item including your plan, breaking the problem down into smaller tickets where it makes sense.
-Include relevant source files, documentation, and context about each ticket so the work has the higest probability of success without additional context being required.
-Do not implement any tickets.