schub 0.1.22 → 0.1.23

package/README.md

@@ -64,11 +64,13 @@ Project-scoped DB commands use the project id from `.schub/config.json`.
 
 #### Proposals
 
-- `schub proposals create` - Create a new proposal locally and in the database.
+- `schub proposals write` - Write a new proposal locally from the template (allocates a DB shorthand but does not upload).
+- `schub proposals create` - Create a proposal directly in the database with `--content` (programmatic/API use).
 - `schub proposals save` - Save all files in one proposal folder to DB/storage (`--proposal-id`) or save all local proposals (`--all`).
 - `schub proposals pull` - Pull a proposal from the database into the local `.schub` folder (requires local `.schub/config.json`).
-- `schub proposals update` - Update a proposal status in frontmatter.
+- `schub proposals update` - Update a proposal status in frontmatter and sync to DB.
 - `schub proposals list` - List proposals (`--show-all` includes archived/rejected).
+- `schub proposals files` - List local and DB files for a proposal (`--id`).
 - `schub proposals archive` - Archive a proposal (use `--skip-tickets` to keep tickets active).
 - `schub proposals delete` - Delete a proposal and clear linked tickets.
 
@@ -96,13 +98,15 @@ schub proposals pull --proposal-id P0003
 
 #### Ticket Management
 
-- `schub tickets create` - Create a ticket from the ticket template.
+- `schub tickets write` - Write a new ticket locally from the template (allocates a DB shorthand but does not upload).
+- `schub tickets create` - Create a ticket directly in the database with `--content` (programmatic/API use).
 - `schub tickets list` - List all tickets in the current project context.
 - `schub tickets check` - Toggle a checklist item in a ticket.
 - `schub tickets update` - Move backlog tickets to any ticket status configured for the project in DB.
 - `schub tickets implement` - Move a ticket to `wip` and launch Opencode.
 - `schub tickets save` - Validate and save one ticket (`--id`) or all local tickets (`--all`) to DB/storage.
 - `schub tickets pull` - Pull tickets from the database into the local `.schub/tickets` folder (requires local `.schub/config.json`).
+- `schub tickets files` - List local and DB files for a ticket (`--id`).
 
 ##### Ticket implementation
 
@@ -136,12 +140,15 @@ schub tickets update --id T0004 --id T0005 --status reviewed
 In Overview view, press `s` on a selected backlog or reviewed ticket to open the status modal.
 For backlog tickets choose `Reviewed` or `Archive`. For reviewed tickets choose `Backlog` or `Archive`, then press enter to confirm or esc to cancel.
 
-#### Reviews & Documentation
+#### Templates & Reviews
 
+- `schub templates create --name adr` - Create a new Architectural Decision Record file.
+- `schub templates create --name cookbook` - Create a new cookbook file.
+- `schub templates create --name review` - Create a `REVIEW_ME.md` file.
+- `schub templates list` - List all templates in the database.
+- `schub templates save` - Save local `.schub/templates/*.md` files to the database (`--name` for one, or all).
+- `schub templates pull` - Pull templates from the database to local `.schub/templates/` (`--name` for one, or all).
 - `schub review complete` - Finalize a review, converting questions into a Q&A section.
-- `schub template create --name adr` - Create a new Architectural Decision Record file.
-- `schub template create --name cookbook` - Create a new cookbook file.
-- `schub template create --name review` - Create a `REVIEW_ME.md` file.
 
 ## LLM Skills
 
@@ -150,6 +157,16 @@ For backlog tickets choose `Reviewed` or `Archive`. For reviewed tickets choose
 - `create-tickets-for-proposal` - Generate actionable ticket files under `.schub/tickets/` from a proposal id.
 - `implement-ticket` - Implement a single ticket end-to-end and move it across ticket status folders.
 - `review-proposal` - Run a proposal review session with open questions and Q&A updates.
+- `refine-ticket` - Refine an existing ticket into the ticket template.
+
+### LLM Workflow
+
+LLMs should **write** locally, then **update/save**:
+
+1. `proposals write` / `tickets write` — scaffold a local file from a template
+2. Edit the local file with concrete details
+3. `proposals update` / `tickets update` — update status (syncs to DB)
+4. `proposals save` / `tickets save` — persist all local files to DB storage
 
 ## Contributing