@picoai/tickets 0.2.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (18) hide show
  1. package/.tickets/spec/AGENTS_EXAMPLE.md +7 -4
  2. package/.tickets/spec/TICKETS.md +302 -383
  3. package/.tickets/spec/profile/defaults.yml +31 -0
  4. package/.tickets/spec/version/20260317-2-tickets-spec.md +106 -0
  5. package/.tickets/spec/version/20260317-tickets-spec.md +82 -0
  6. package/README.md +140 -184
  7. package/package.json +2 -1
  8. package/release-history.json +14 -0
  9. package/src/cli.js +479 -115
  10. package/src/lib/claims.js +66 -0
  11. package/src/lib/config.js +176 -0
  12. package/src/lib/constants.js +11 -2
  13. package/src/lib/index.js +241 -0
  14. package/src/lib/listing.js +24 -84
  15. package/src/lib/planning.js +452 -0
  16. package/src/lib/projections.js +79 -0
  17. package/src/lib/repair.js +1 -1
  18. package/src/lib/validation.js +380 -2
package/.tickets/spec/AGENTS_EXAMPLE.md CHANGED
@@ -1,16 +1,19 @@
1
1
  This file is an example for agent harnesses. Rename or copy it to `AGENTS.md` if your tooling reads it.
2
2
 
3
- The purpose of this bootstrap is to ensure an agent loads the canonical workflow from `TICKETS.md` before doing any work.
3
+ The purpose of this bootstrap is to ensure an agent loads the canonical ticketing workflow before doing any work.
4
4
 
5
5
  ## Ticketing Workflow
6
6
 
7
7
  ### Required Behavior
8
- - First action: open and read `TICKETS.md` (canonical ticket workflow and rules).
9
- - First response: briefly confirm understanding of the ticketing system described in `TICKETS.md` before starting any implementation work.
8
+ - First action: if your environment supports repo-local skills and `.tickets/skills/tickets/SKILL.md` exists, load that skill. Otherwise open and read `TICKETS.md`.
9
+ - First response: briefly confirm understanding of the ticketing system before starting any implementation work.
10
+ - Before interpreting planning language or creating tickets, consult `.tickets/config.yml` for repo-local defaults and semantic overrides.
11
+ - When the human uses feature/phase/milestone/roadmap or custom repo terms, keep using their vocabulary in the conversation and translate it into the generic CLI planning fields internally.
10
12
  - Use the repo-local CLI (`npx @picoai/tickets`) as the integration surface for tickets and logs.
11
13
  - Before performing work on a ticket, validate it: run `npx @picoai/tickets validate` (or `npx @picoai/tickets validate --issues` + `npx @picoai/tickets repair`).
12
14
  - When logging via the CLI: use `npx @picoai/tickets log --machine` so logs are strictly structured.
13
- - Respect `assignment.mode` and any `agent_limits` in the ticket/config.
15
+ - Respect `assignment.mode`, `agent_limits`, active advisory claims, and repo-local defaults in `.tickets/config.yml`.
14
16
 
15
17
  ### Bootstrapping TICKETS.md
16
18
  - If `.tickets/` or `TICKETS.md` are missing, run `npx @picoai/tickets init`.
19
+ - `init` also creates `.tickets/config.yml` and `.tickets/skills/tickets/SKILL.md`.