@hasna/todos 0.11.42 → 0.11.44

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.
package/README.md CHANGED
@@ -246,11 +246,15 @@ MCP clients get the same local coordination through `claim_next_task`,
246
246
 
247
247
  ## Local Plan Templates
248
248
 
249
- Reusable plan templates also live in the local SQLite database. They can create
250
- one task or a full ordered plan with dependencies, variables, priorities, tags,
251
- and descriptions:
249
+ Reusable plan templates live in the local SQLite database. The package also
250
+ ships a marketplace-free local library for bug fixes, feature implementation,
251
+ security review, releases, migrations, incidents, docs refreshes, QA, and open
252
+ source package bootstraps. Templates can create one task or a full ordered plan
253
+ with dependencies, variables, priorities, tags, and descriptions:
252
254
 
253
255
  ```bash
256
+ todos template-library --json
257
+ todos template-library --write .todos/templates
254
258
  todos template-init
255
259
  todos template-preview <template-id> --var name=api
256
260
  todos templates --use <template-id> --var name=api
@@ -258,12 +262,16 @@ todos template-export <template-id> > plan-template.json
258
262
  todos template-import plan-template.json
259
263
  ```
260
264
 
261
- `todos templates --use` creates every task in a multi-task template and wires
262
- its local dependency graph, so agents can immediately run `todos ready`,
263
- `todos blocked`, or `todos deps <task-id> --graph` against the generated plan.
264
- The same local-only workflow is available to MCP clients through
265
- `create_template`, `list_templates`, `create_task_from_template`,
266
- `preview_template`, `export_template`, and `import_template`.
265
+ `todos template-library --write` writes editable JSON files that use the same
266
+ shape as `todos template-import`, so teams can fork a built-in workflow without
267
+ contacting any hosted marketplace. `todos templates --use` creates every task in
268
+ a multi-task template and wires its local dependency graph, so agents can
269
+ immediately run `todos ready`, `todos blocked`, or
270
+ `todos deps <task-id> --graph` against the generated plan. The same local-only
271
+ workflow is available to MCP clients through `list_template_library`,
272
+ `write_template_library`, `init_templates`, `create_template`, `list_templates`,
273
+ `create_task_from_template`, `preview_template`, `export_template`, and
274
+ `import_template`.
267
275
 
268
276
  ## Local Git Traceability
269
277
 
@@ -0,0 +1,3 @@
1
+ import type { Command } from "commander";
2
+ export declare function registerEnvironmentSnapshotCommands(program: Command): void;
3
+ //# sourceMappingURL=environment-snapshots.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"environment-snapshots.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/environment-snapshots.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAWzC,wBAAgB,mCAAmC,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CA+E1E"}
@@ -1 +1 @@
1
- {"version":3,"file":"plan-template-commands.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/plan-template-commands.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAazC,wBAAgB,4BAA4B,CAAC,OAAO,EAAE,OAAO,QAsX5D"}
1
+ {"version":3,"file":"plan-template-commands.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/plan-template-commands.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAazC,wBAAgB,4BAA4B,CAAC,OAAO,EAAE,OAAO,QAka5D"}