tcw-cli 3.0.2__tar.gz → 4.0.0__tar.gz
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.
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/PKG-INFO +194 -164
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/README.md +193 -163
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/pyproject.toml +1 -1
- tcw_cli-4.0.0/tcw/__init__.py +1 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/capabilities/cli.py +149 -95
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/cli.py +239 -291
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/cli_help.py +5 -2
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/cli_suggest.py +21 -3
- tcw_cli-4.0.0/tcw/config.py +1513 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/config_cli.py +57 -29
- tcw_cli-4.0.0/tcw/config_keys.py +260 -0
- tcw_cli-4.0.0/tcw/errors.py +153 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/exit.py +4 -1
- tcw_cli-4.0.0/tcw/ids.py +477 -0
- tcw_cli-4.0.0/tcw/locate.py +281 -0
- tcw_cli-4.0.0/tcw/migrate/__init__.py +7 -0
- tcw_cli-4.0.0/tcw/migrate/cli.py +264 -0
- tcw_cli-4.0.0/tcw/migrate/config.py +1392 -0
- tcw_cli-4.0.0/tcw/migrate/editors.py +67 -0
- tcw_cli-4.0.0/tcw/migrate/execute.py +372 -0
- tcw_cli-4.0.0/tcw/migrate/family.py +309 -0
- tcw_cli-4.0.0/tcw/migrate/jira.py +197 -0
- tcw_cli-4.0.0/tcw/migrate/legacy.py +995 -0
- tcw_cli-4.0.0/tcw/migrate/loose.py +160 -0
- tcw_cli-4.0.0/tcw/migrate/model.py +163 -0
- tcw_cli-4.0.0/tcw/migrate/overrides.py +283 -0
- tcw_cli-4.0.0/tcw/migrate/plan.py +555 -0
- tcw_cli-4.0.0/tcw/migrate/progress.py +113 -0
- tcw_cli-4.0.0/tcw/migrate/record.py +62 -0
- tcw_cli-4.0.0/tcw/migrate/references.py +223 -0
- tcw_cli-4.0.0/tcw/migrate/report.py +182 -0
- tcw_cli-4.0.0/tcw/migrate/stores.py +576 -0
- tcw_cli-4.0.0/tcw/move.py +522 -0
- tcw_cli-4.0.0/tcw/object_folders.py +562 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/output.py +25 -3
- tcw_cli-4.0.0/tcw/ownership.py +84 -0
- tcw_cli-4.0.0/tcw/project_cli.py +360 -0
- tcw_cli-4.0.0/tcw/project_files.py +206 -0
- tcw_cli-4.0.0/tcw/projects_cli.py +74 -0
- tcw_cli-4.0.0/tcw/provision.py +575 -0
- tcw_cli-4.0.0/tcw/reference_fields.py +130 -0
- tcw_cli-4.0.0/tcw/refs.py +98 -0
- tcw_cli-4.0.0/tcw/rewrite.py +508 -0
- tcw_cli-4.0.0/tcw/scope.py +212 -0
- tcw_cli-4.0.0/tcw/serve/dist/client/assets/index-wKjMdQQ-.js +122 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/dist/client/index.html +1 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/files.py +50 -12
- tcw_cli-4.0.0/tcw/serve/records.py +396 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/server.py +47 -4
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/services.py +2 -12
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/work.py +302 -102
- tcw_cli-4.0.0/tcw/store/base.py +1784 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/store/config_edit.py +269 -22
- tcw_cli-4.0.0/tcw/store/fs.py +4433 -0
- tcw_cli-4.0.0/tcw/store/links.py +134 -0
- tcw_cli-4.0.0/tcw/store/manifest.py +184 -0
- tcw_cli-4.0.0/tcw/store/project.py +2424 -0
- tcw_cli-4.0.0/tcw/taxonomy/cli.py +203 -0
- tcw_cli-4.0.0/tcw/tree_scope.py +462 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/validate.py +384 -98
- tcw_cli-4.0.0/tcw/work/backend.py +163 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/cli.py +420 -171
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/config.py +27 -16
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/fs_backend.py +192 -127
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/gates.py +117 -120
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/hooks.py +4 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/backend.py +628 -114
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/client.py +43 -4
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/config.py +8 -71
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/jql.py +4 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/remote.py +53 -12
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/tickets.py +47 -176
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/layout.py +12 -7
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/model.py +104 -43
- tcw_cli-4.0.0/tcw/work/open.py +291 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/audit-backlog.md +36 -21
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/pause-work.md +5 -3
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/search.md +27 -17
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/plan.md +10 -9
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/record.py +2 -1
- tcw_cli-4.0.0/tcw/work/references.py +117 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/resolve.py +1 -1
- tcw_cli-4.0.0/tcw/work/scoped.py +189 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/PKG-INFO +194 -164
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/SOURCES.txt +97 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_capabilities.py +128 -112
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_capabilities_cli_contract.py +29 -21
- tcw_cli-4.0.0/tests/test_capabilities_federation.py +718 -0
- tcw_cli-4.0.0/tests/test_capabilities_reset.py +190 -0
- tcw_cli-4.0.0/tests/test_capabilities_rm.py +469 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_capability_ref_wording.py +112 -81
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_check_versions.py +4 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_cli_contract.py +109 -125
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_cli_handler.py +20 -16
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_cli_help_standard.py +21 -9
- tcw_cli-4.0.0/tests/test_combine.py +346 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_command_suggestions.py +40 -0
- tcw_cli-4.0.0/tests/test_config_command_state.py +69 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_config_edit.py +182 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_config_edit_writers.py +65 -156
- tcw_cli-4.0.0/tests/test_config_environment.py +291 -0
- tcw_cli-4.0.0/tests/test_config_keys.py +72 -0
- tcw_cli-4.0.0/tests/test_config_overrides.py +123 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_configuration_text_home.py +6 -9
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_cut_version.py +43 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_docs_describe_3_0.py +37 -3
- tcw_cli-4.0.0/tests/test_docs_describe_4_0.py +188 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_documentation_config.py +4 -3
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_documentation_prompt.py +9 -8
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_documented_cli_surface.py +35 -1
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_environment_hardness.py +121 -98
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_eval_fixture.py +13 -10
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_eval_grading.py +7 -6
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_eval_runner.py +3 -2
- tcw_cli-4.0.0/tests/test_exit_code_tables.py +44 -0
- tcw_cli-4.0.0/tests/test_families.py +33 -0
- tcw_cli-4.0.0/tests/test_fetch_project.py +450 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_findings_type.py +9 -7
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_git_example.py +67 -7
- tcw_cli-4.0.0/tests/test_identifier_length.py +139 -0
- tcw_cli-4.0.0/tests/test_identifier_sweep.py +105 -0
- tcw_cli-4.0.0/tests/test_ids.py +308 -0
- tcw_cli-4.0.0/tests/test_inherited_config.py +1106 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_init_configured_tree_path.py +17 -16
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_init_provision_contract.py +11 -10
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_item_tags_read.py +2 -1
- tcw_cli-4.0.0/tests/test_ledger_3_0.py +98 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_legacy_store_config.py +68 -48
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_lifecycle_config_tags.py +3 -2
- tcw_cli-4.0.0/tests/test_links_full_identifiers.py +128 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_literal_store_names.py +21 -7
- tcw_cli-4.0.0/tests/test_load_order.py +346 -0
- tcw_cli-4.0.0/tests/test_locate.py +239 -0
- tcw_cli-4.0.0/tests/test_manifest.py +220 -0
- tcw_cli-4.0.0/tests/test_manifest_cli.py +603 -0
- tcw_cli-4.0.0/tests/test_manifest_cousins.py +256 -0
- tcw_cli-4.0.0/tests/test_manifest_worktree.py +518 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_migration_guide.py +47 -1
- tcw_cli-4.0.0/tests/test_migration_guide_4_0.py +381 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_multiproject.py +35 -42
- tcw_cli-4.0.0/tests/test_no_3x_inheritance.py +183 -0
- tcw_cli-4.0.0/tests/test_no_extends.py +176 -0
- tcw_cli-4.0.0/tests/test_object_folder_shape.py +256 -0
- tcw_cli-4.0.0/tests/test_object_folder_sweep.py +185 -0
- tcw_cli-4.0.0/tests/test_object_folders.py +261 -0
- tcw_cli-4.0.0/tests/test_object_walk.py +129 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_override_in_linked_worktree.py +13 -6
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_override_letter_case.py +4 -4
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_override_references.py +38 -33
- tcw_cli-4.0.0/tests/test_overrides_by_path.py +1303 -0
- tcw_cli-4.0.0/tests/test_ownership.py +110 -0
- tcw_cli-4.0.0/tests/test_ownership_sweep.py +232 -0
- tcw_cli-4.0.0/tests/test_owning_project.py +241 -0
- tcw_cli-4.0.0/tests/test_parent_links.py +522 -0
- tcw_cli-4.0.0/tests/test_parent_links_cli.py +741 -0
- tcw_cli-4.0.0/tests/test_parent_links_parse.py +102 -0
- tcw_cli-4.0.0/tests/test_parent_links_static.py +205 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_partial_removal.py +14 -13
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_procedure_config.py +4 -3
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_procedure_verb.py +3 -2
- tcw_cli-4.0.0/tests/test_project_files.py +166 -0
- tcw_cli-4.0.0/tests/test_project_files_cli.py +712 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_project_graph_paths.py +10 -4
- tcw_cli-4.0.0/tests/test_project_group.py +97 -0
- tcw_cli-4.0.0/tests/test_project_info.py +257 -0
- tcw_cli-4.0.0/tests/test_project_lookup.py +713 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_project_overrides.py +40 -100
- tcw_cli-4.0.0/tests/test_project_path.py +124 -0
- tcw_cli-4.0.0/tests/test_project_placement.py +140 -0
- tcw_cli-4.0.0/tests/test_project_provision.py +1181 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_project_registry.py +149 -313
- tcw_cli-4.0.0/tests/test_projectfiles_helper.py +51 -0
- tcw_cli-4.0.0/tests/test_projects_list.py +250 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_prompt_fallback.py +10 -1
- tcw_cli-4.0.0/tests/test_reference_fields.py +186 -0
- tcw_cli-4.0.0/tests/test_refs.py +163 -0
- tcw_cli-4.0.0/tests/test_removal_blockers.py +84 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_require_artifact.py +5 -4
- tcw_cli-4.0.0/tests/test_rewrite.py +295 -0
- tcw_cli-4.0.0/tests/test_rewrite_values.py +56 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_routing_nodes.py +12 -9
- tcw_cli-4.0.0/tests/test_run_in_folder.py +314 -0
- tcw_cli-4.0.0/tests/test_scope_members.py +135 -0
- tcw_cli-4.0.0/tests/test_scope_reader.py +209 -0
- tcw_cli-4.0.0/tests/test_scope_rows.py +169 -0
- tcw_cli-4.0.0/tests/test_scope_trees.py +597 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_session_bootstrap.py +62 -5
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_shipped_procedures.py +25 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_shipped_prompts.py +36 -8
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_shipped_text.py +63 -3
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_skill_flow.py +4 -4
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_smoke.py +16 -13
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_stage_verb.py +3 -2
- tcw_cli-4.0.0/tests/test_state_files.py +165 -0
- tcw_cli-4.0.0/tests/test_statefiles_helper.py +44 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_static_guards.py +22 -6
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_stdin_cli.py +4 -3
- tcw_cli-4.0.0/tests/test_store_addresses.py +382 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_store_bounds.py +25 -15
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_store_editor.py +52 -60
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_store_nodes.py +28 -18
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_store_provisioning.py +312 -624
- tcw_cli-4.0.0/tests/test_stored_references.py +166 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_subprocess_stdin.py +8 -4
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_taxonomy.py +301 -344
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_taxonomy_cli_contract.py +24 -28
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_taxonomy_rm_gaps.py +43 -22
- tcw_cli-4.0.0/tests/test_tree_full_identifiers.py +249 -0
- tcw_cli-4.0.0/tests/test_tree_inheritance.py +316 -0
- tcw_cli-4.0.0/tests/test_tree_move.py +436 -0
- tcw_cli-4.0.0/tests/test_tree_parent_missing.py +466 -0
- tcw_cli-4.0.0/tests/test_tree_parents.py +377 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_tree_store_files_only.py +9 -7
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_tree_store_raises.py +13 -2
- tcw_cli-4.0.0/tests/test_upcoming_entries.py +121 -0
- tcw_cli-4.0.0/tests/test_upstream_projects.py +507 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_validate.py +98 -50
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_validate_command.py +27 -35
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_validate_moved_stores.py +25 -18
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_validate_target.py +27 -19
- tcw_cli-4.0.0/tests/test_worktree_remote_forms.py +175 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_worktree_sibling_nodes.py +45 -32
- tcw_cli-3.0.2/tcw/__init__.py +0 -1
- tcw_cli-3.0.2/tcw/config.py +0 -655
- tcw_cli-3.0.2/tcw/errors.py +0 -89
- tcw_cli-3.0.2/tcw/projects_cli.py +0 -77
- tcw_cli-3.0.2/tcw/refs.py +0 -170
- tcw_cli-3.0.2/tcw/serve/dist/client/assets/index-BGwvKkRc.js +0 -122
- tcw_cli-3.0.2/tcw/serve/records.py +0 -254
- tcw_cli-3.0.2/tcw/store/base.py +0 -1016
- tcw_cli-3.0.2/tcw/store/fs.py +0 -3520
- tcw_cli-3.0.2/tcw/store/project.py +0 -1110
- tcw_cli-3.0.2/tcw/taxonomy/cli.py +0 -201
- tcw_cli-3.0.2/tcw/work/backend.py +0 -113
- tcw_cli-3.0.2/tcw/work/open.py +0 -241
- tcw_cli-3.0.2/tcw/work/references.py +0 -88
- tcw_cli-3.0.2/tests/test_capabilities_federation.py +0 -735
- tcw_cli-3.0.2/tests/test_capabilities_reset.py +0 -148
- tcw_cli-3.0.2/tests/test_capabilities_rm.py +0 -409
- tcw_cli-3.0.2/tests/test_ledger_3_0.py +0 -54
- tcw_cli-3.0.2/tests/test_projects_list.py +0 -186
- tcw_cli-3.0.2/tests/test_refs.py +0 -235
- tcw_cli-3.0.2/tests/test_upcoming_entries.py +0 -90
- tcw_cli-3.0.2/tests/test_upstream_projects.py +0 -672
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/LICENSE +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/setup.cfg +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/capabilities/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/findings.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/dist/client/assets/index-DkarCRfj.css +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/serve/dist/client/theme-init.js +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/stdin.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/store/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/store/checkouts.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/store/yaml_source.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/taxonomy/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/advance.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/generate.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/__init__.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/jira/mapping.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/passages.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/create-work.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/documentation-sync.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/triage-issues.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/procedures/unattended-work.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/implement.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/inbox.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/postmortem.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/qa.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/request.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/review.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw/work/prompts/spec.md +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/dependency_links.txt +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/entry_points.txt +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/requires.txt +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tcw_cli.egg-info/top_level.txt +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_cli_guide.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_committed_paths.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_doc_vocabulary.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_documentation_sync_wiring.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_dynamic_skill_marker.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_eval_coverage.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_eval_files_changed.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_falsification_rule.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_generate_hook.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_no_node.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_plugin_manifests.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_remote_session_setup.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_repo_lifecycle.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_skill_path_pointers.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_stdin.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_suite_runs_its_own_tcw.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_unattended_work_skill.py +0 -0
- {tcw_cli-3.0.2 → tcw_cli-4.0.0}/tests/test_unpushed_version_script.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: tcw-cli
|
|
3
|
-
Version:
|
|
3
|
+
Version: 4.0.0
|
|
4
4
|
Summary: Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project.
|
|
5
5
|
License: Apache License
|
|
6
6
|
Version 2.0, January 2004
|
|
@@ -292,9 +292,10 @@ Or, in the Claude **web app** or **desktop app**, open the plugin directory, add
|
|
|
292
292
|
`brocef/TCW` as a marketplace, and install `tcw` from it — no terminal needed.
|
|
293
293
|
|
|
294
294
|
**Then start a new session.** The plugin installs the `tcw` CLI at session start
|
|
295
|
-
by installing
|
|
296
|
-
|
|
297
|
-
|
|
295
|
+
by installing, from PyPI with `pipx`, the `tcw-cli` release whose version is the
|
|
296
|
+
plugin's own, so a plugin update brings the matching CLI. A plugin installed
|
|
297
|
+
mid-session cannot run its CLI until the next session begins. That first session
|
|
298
|
+
needs network access. It installs over an existing `pipx install tcw-cli` rather than beside it, and
|
|
298
299
|
leaves a development checkout (`pip install -e .`) alone. If `tcw` goes missing
|
|
299
300
|
anyway, `pipx install tcw-cli` is the whole fix — the **`setup`** skill
|
|
300
301
|
carries the cases where it is not. When the `tcw` CLI and the plugin's skills
|
|
@@ -444,11 +445,14 @@ if ! command -v tcw >/dev/null 2>&1 && [ -x "$userbin/tcw" ]; then
|
|
|
444
445
|
fi
|
|
445
446
|
```
|
|
446
447
|
|
|
447
|
-
**If your
|
|
448
|
-
repository it cloned, so
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
|
|
448
|
+
**If your project has related projects, or a store in another repository**,
|
|
449
|
+
the container holds only the repository it cloned, so those are named but
|
|
450
|
+
absent. Run `tcw project provision` after the install: it clones each related
|
|
451
|
+
project and each store that the project's manifests name with a repository and
|
|
452
|
+
that this machine does not have, into the folder the manifest gives, and does
|
|
453
|
+
nothing on a machine that already holds them. A **manifest**,
|
|
454
|
+
`.tcw/tcw-manifest.yaml`, is the file that says where each related project is.
|
|
455
|
+
See [Related projects](docs/guide/multi-repo.md).
|
|
452
456
|
|
|
453
457
|
Installing the **plugin** in a Claude Code session is a separate step from
|
|
454
458
|
installing the CLI, and only needed where the harness does not carry your plugins
|
|
@@ -466,34 +470,47 @@ it changes. None of them copies another's content.
|
|
|
466
470
|
|
|
467
471
|
Taxonomy and capabilities are plain files in the repository, so a code change
|
|
468
472
|
and the description of what it changed travel in the same commit and the same
|
|
469
|
-
pull request. A work item is a **folder that
|
|
470
|
-
property recorded about it (a value, not a location), and its documents stay in
|
|
471
|
-
the same folder from the first stage to the last
|
|
472
|
-
|
|
473
|
+
pull request. A work item is a **folder that does not move when its stage
|
|
474
|
+
changes**: its stage is a property recorded about it (a value, not a location), and its documents stay in
|
|
475
|
+
the same folder from the first stage to the last, beside its **state file**,
|
|
476
|
+
`tcw-work-item.yaml`, which in a filesystem-mode project holds its properties;
|
|
477
|
+
any other file of its own goes in its `resources/` folder ([The Work component](docs/guide/work.md)).
|
|
478
|
+
|
|
479
|
+
Every object, whether a work item, a taxonomy entry or a capability, is named by
|
|
480
|
+
its **full identifier**, `<project>.<namespace>/<id-path>`: the project's ID,
|
|
481
|
+
the axis, and the object's path inside it, such as
|
|
482
|
+
`my-app.work/2026-09-15-export-invoices-as-pdf` or
|
|
483
|
+
`my-app.taxonomy/invoice`. "Slug" is a nickname for it. A link from one object
|
|
484
|
+
to another is written `tcw://` followed by the full identifier, and
|
|
485
|
+
`tcw validate` checks that it resolves
|
|
486
|
+
([Linking and validation](docs/guide/linking-and-validation.md)).
|
|
473
487
|
|
|
474
488
|
**One command-line tool, `tcw`**, does everything:
|
|
475
489
|
|
|
476
|
-
| Command | What it does
|
|
477
|
-
| ------------------------- |
|
|
478
|
-
| `tcw
|
|
479
|
-
| `tcw provision`
|
|
490
|
+
| Command | What it does |
|
|
491
|
+
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
492
|
+
| `tcw project new` | marks a folder as a TCW project and creates the folders for each axis |
|
|
493
|
+
| `tcw project provision` | clones the related projects and stores this project's manifests name but this machine lacks |
|
|
494
|
+
| `tcw project info` | shows how the project is assembled: its parents, children, load order (the order its ancestors are read in, a later one's value winning), settings, stores and overrides |
|
|
495
|
+
| `tcw project path` | prints a related project's folder on this machine |
|
|
496
|
+
| `tcw migrate` | converts a TCW 3.x project to 4.0 ([the migration guide](docs/migration-guide-3.X-to-4.0.0.md)) |
|
|
480
497
|
| `tcw validate [--remote]` | checks every file, reference and link in the project; in a Jira-mode project the item references, stages and declared record changes are checked only with `--remote`, which also checks the Jira workflow |
|
|
481
|
-
| `tcw
|
|
482
|
-
| `tcw config
|
|
483
|
-
| `tcw serve` | starts a local web app for reading and editing all three axes
|
|
484
|
-
| `tcw taxonomy` | the vocabulary and features
|
|
485
|
-
| `tcw capabilities` | what a user can do
|
|
486
|
-
| `tcw work` | the changes, and the stages each one moves through
|
|
498
|
+
| `tcw project list` | lists this project and every project related to it |
|
|
499
|
+
| `tcw project config` | prints the configuration commands run with; `--origin` says where each value came from |
|
|
500
|
+
| `tcw serve` | starts a local web app for reading and editing all three axes |
|
|
501
|
+
| `tcw taxonomy` | the vocabulary and features |
|
|
502
|
+
| `tcw capabilities` | what a user can do |
|
|
503
|
+
| `tcw work` | the changes, and the stages each one moves through |
|
|
487
504
|
|
|
488
505
|
A repository adopts TCW with one command:
|
|
489
506
|
|
|
490
507
|
```sh
|
|
491
|
-
tcw
|
|
492
|
-
tcw
|
|
508
|
+
tcw project new --id my-project # all three axes
|
|
509
|
+
tcw project new --id my-project taxonomy work # …or only some of them
|
|
493
510
|
```
|
|
494
511
|
|
|
495
|
-
That writes
|
|
496
|
-
under `docs/`. A project can adopt the work axis alone and add the others later.
|
|
512
|
+
That writes `.tcw/tcw-config.yaml` holding the project's ID and creates the
|
|
513
|
+
folders under `docs/`. A project can adopt the work axis alone and add the others later.
|
|
497
514
|
`tcw validate` exits non-zero on any error, so it works as a check in CI. What
|
|
498
515
|
every command prints, and its exit codes, are in
|
|
499
516
|
[the command-line guide](docs/guide/cli.md).
|
|
@@ -505,15 +522,20 @@ means, writing a spec, or judging whether work is finished is what the plugin's
|
|
|
505
522
|
skills guide an agent through. See [Skills and Agents](#skills-and-agents).
|
|
506
523
|
|
|
507
524
|
**Many repositories, one model.** Projects are identified by ID, never by path.
|
|
508
|
-
A project
|
|
509
|
-
`tcw-config.yaml`,
|
|
510
|
-
|
|
511
|
-
|
|
512
|
-
|
|
513
|
-
|
|
514
|
-
|
|
515
|
-
|
|
516
|
-
|
|
525
|
+
A project names the projects it inherits from as its **parents**, under
|
|
526
|
+
`parents:` in `.tcw/tcw-config.yaml`, each with what it passes down
|
|
527
|
+
(`inherit`: `all`, the default, `none`, or a list drawn from `taxonomy`,
|
|
528
|
+
`capabilities` and `config`), and may
|
|
529
|
+
name its **children** under `children:`. A library others read needs to name
|
|
530
|
+
none of its readers: a private project can name a public one as a parent that
|
|
531
|
+
never names it back. Where each related project sits on this machine is in the
|
|
532
|
+
project's manifests, never in its configuration. Every object of a related
|
|
533
|
+
project is named by its full identifier, and only the project that owns an
|
|
534
|
+
object changes it: a command run elsewhere is refused and names the folder to
|
|
535
|
+
run it in, with `tcw -C <folder>`. A checkout holding only some of the related
|
|
536
|
+
repositories still works: a command that needs an absent project says so and
|
|
537
|
+
names `tcw project provision`. See [Related projects](docs/guide/multi-repo.md)
|
|
538
|
+
and [Configuration](docs/guide/configuration.md).
|
|
517
539
|
|
|
518
540
|
## Why taxonomy and capabilities live in the repository
|
|
519
541
|
|
|
@@ -548,9 +570,11 @@ already exists, so vocabulary is registered first.
|
|
|
548
570
|
Entries form a tree, and an entry's path is its address: `admin/permission` and
|
|
549
571
|
`billing/permission` are two different entries.
|
|
550
572
|
|
|
551
|
-
A project
|
|
552
|
-
|
|
553
|
-
|
|
573
|
+
A project **inherits** the taxonomy of each parent whose `inherit` includes
|
|
574
|
+
taxonomy, at every level up. An inherited entry is read by its path like one of
|
|
575
|
+
your own, and its full identifier (`acme.taxonomy/permission`) names the project
|
|
576
|
+
it belongs to. To change an inherited entry, a project puts its own entry at the
|
|
577
|
+
same path, holding only what it changes: an **override**.
|
|
554
578
|
|
|
555
579
|
### Usage
|
|
556
580
|
|
|
@@ -565,18 +589,21 @@ described in [Skills and Agents](#skills-and-agents).
|
|
|
565
589
|
|
|
566
590
|
#### CLI
|
|
567
591
|
|
|
568
|
-
| Command
|
|
569
|
-
|
|
|
570
|
-
| `tcw taxonomy list`
|
|
571
|
-
| `tcw taxonomy add`
|
|
572
|
-
| `tcw taxonomy show`
|
|
573
|
-
| `tcw taxonomy path`
|
|
574
|
-
| `tcw taxonomy
|
|
575
|
-
| `tcw taxonomy
|
|
576
|
-
| `tcw taxonomy
|
|
577
|
-
|
|
578
|
-
|
|
579
|
-
`tcw
|
|
592
|
+
| Command | What it does |
|
|
593
|
+
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
594
|
+
| `tcw taxonomy list` | prints the full identifier of each of this project's own entries; `--scope up` adds the inherited ones |
|
|
595
|
+
| `tcw taxonomy add` | creates a vocabulary entry or a feature; its description from standard input; at an inherited path, writes an override holding only what differs |
|
|
596
|
+
| `tcw taxonomy show` | prints one entry |
|
|
597
|
+
| `tcw taxonomy path` | prints the folder the taxonomy is stored in |
|
|
598
|
+
| `tcw taxonomy rename` | renames an entry's last part, rewriting every reference to it in this project |
|
|
599
|
+
| `tcw taxonomy move` | moves an entry into another entry (`--into`) or to the top (`--top`), rewriting every reference to it in this project |
|
|
600
|
+
| `tcw taxonomy rm` | removes a local entry nothing is nested under or refers to, an override included |
|
|
601
|
+
| `tcw taxonomy search` | searches entry names and descriptions |
|
|
602
|
+
|
|
603
|
+
Creating the taxonomy's folder is `tcw project new taxonomy`, and checking it is
|
|
604
|
+
`tcw validate`. Which projects a taxonomy is inherited from is set by the
|
|
605
|
+
project's parent links (`parents:` in `.tcw/tcw-config.yaml`), not by a
|
|
606
|
+
taxonomy command.
|
|
580
607
|
|
|
581
608
|
```sh
|
|
582
609
|
echo "A bill issued to a customer." | tcw taxonomy add Invoice # vocabulary by default
|
|
@@ -584,7 +611,6 @@ echo "Running the shop." | tcw taxonomy add Admin
|
|
|
584
611
|
tcw taxonomy add Permission --parent admin # → admin/permission
|
|
585
612
|
tcw taxonomy add "PDF Export" --kind feature --vocab invoice
|
|
586
613
|
tcw taxonomy list
|
|
587
|
-
tcw taxonomy extends add acme-shared # inherit another project
|
|
588
614
|
```
|
|
589
615
|
|
|
590
616
|
More in [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md).
|
|
@@ -594,17 +620,17 @@ More in [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md).
|
|
|
594
620
|
### Overview
|
|
595
621
|
|
|
596
622
|
A capability is one thing a user can do, such as "Download an invoice as PDF".
|
|
597
|
-
Each is addressed by a path (`billing/invoices`),
|
|
598
|
-
|
|
599
|
-
`Omitted`. The status is what makes the list useful: it says what the product
|
|
623
|
+
Each is addressed by a path (`billing/invoices`), and carries a
|
|
624
|
+
**status**: `Supported`, `Partial`, `Missing`, `Blocked` or `Omitted`. The status is what makes the list useful: it says what the product
|
|
600
625
|
actually does today. The `implement` stage changes the record in the same change
|
|
601
626
|
as the code, and `Missing` means a gap the team has acknowledged, never a plan.
|
|
602
627
|
|
|
603
|
-
Capabilities
|
|
604
|
-
mobile app that drive the same server declare
|
|
605
|
-
each **overrides** only what differs, for
|
|
606
|
-
to its description. An override
|
|
607
|
-
|
|
628
|
+
Capabilities are **inherited** from each parent whose `inherit` includes
|
|
629
|
+
capabilities. A web frontend and a mobile app that drive the same server declare
|
|
630
|
+
their shared capabilities once, and each **overrides** only what differs, for
|
|
631
|
+
example marking one `Omitted` or adding to its description. An override is the
|
|
632
|
+
project's own capability at the same path as the inherited one, holding only the
|
|
633
|
+
fields it changes, and can be undone to go back to the inherited version.
|
|
608
634
|
|
|
609
635
|
#### Relationship to Taxonomy
|
|
610
636
|
|
|
@@ -618,34 +644,35 @@ registered in the taxonomy before a capability names it.
|
|
|
618
644
|
|
|
619
645
|
#### Skills
|
|
620
646
|
|
|
621
|
-
| Skill | What it does
|
|
622
|
-
| ---------------------------------------------- |
|
|
647
|
+
| Skill | What it does |
|
|
648
|
+
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
623
649
|
| [`capabilities`](skills/capabilities/SKILL.md) | Guides an agent through a work item that changes what users can do: declaring the change at spec, checking it against the existing capabilities, and changing the records during implement. |
|
|
624
650
|
|
|
625
651
|
#### CLI
|
|
626
652
|
|
|
627
|
-
| Command
|
|
628
|
-
|
|
|
629
|
-
| `tcw capabilities list`
|
|
630
|
-
| `tcw capabilities show`
|
|
631
|
-
| `tcw capabilities path`
|
|
632
|
-
| `tcw capabilities add`
|
|
633
|
-
| `tcw capabilities set`
|
|
634
|
-
| `tcw capabilities reset`
|
|
635
|
-
| `tcw capabilities
|
|
636
|
-
| `tcw capabilities
|
|
637
|
-
| `tcw capabilities
|
|
638
|
-
| `tcw capabilities
|
|
639
|
-
|
|
640
|
-
|
|
641
|
-
`tcw
|
|
653
|
+
| Command | What it does |
|
|
654
|
+
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
|
|
655
|
+
| `tcw capabilities list` | prints this project's own capabilities; `--status` narrows it, `--scope up` adds the inherited ones |
|
|
656
|
+
| `tcw capabilities show` | prints one capability |
|
|
657
|
+
| `tcw capabilities path` | prints the folder capabilities are stored in |
|
|
658
|
+
| `tcw capabilities add` | creates a capability; its body from standard input; refused at an inherited path |
|
|
659
|
+
| `tcw capabilities set` | changes a capability's status or fields; on an inherited one, writes an override at the same path holding only the fields given |
|
|
660
|
+
| `tcw capabilities reset` | removes a local override, going back to the inherited version |
|
|
661
|
+
| `tcw capabilities rename` | renames a capability's last part, rewriting every reference to it in this project |
|
|
662
|
+
| `tcw capabilities move` | moves a capability into another one (`--into`) or to the top (`--top`), rewriting every reference to it in this project |
|
|
663
|
+
| `tcw capabilities rm` | removes a local capability, an override included |
|
|
664
|
+
| `tcw capabilities search` | searches names and descriptions |
|
|
665
|
+
| `tcw capabilities drift` | reports inherited capabilities nobody here has ruled on, and changes finished work declared that today's records do not show |
|
|
666
|
+
|
|
667
|
+
Creating the ledger's folder is `tcw project new capabilities`, and checking it is
|
|
668
|
+
`tcw validate`. Which projects capabilities are inherited from is set by the
|
|
669
|
+
project's parent links (`parents:` in `.tcw/tcw-config.yaml`).
|
|
642
670
|
|
|
643
671
|
```sh
|
|
644
672
|
tcw capabilities add billing/invoices "Download an invoice as PDF" < invoices.md
|
|
645
673
|
tcw capabilities set billing/invoices --field "Subject=invoice" --field "Feature=pdf-export"
|
|
646
674
|
tcw capabilities list --status Missing
|
|
647
675
|
tcw capabilities set billing/invoices --status Supported
|
|
648
|
-
tcw capabilities extends add web-frontend # inherit another project
|
|
649
676
|
```
|
|
650
677
|
|
|
651
678
|
More in [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md).
|
|
@@ -657,8 +684,10 @@ More in [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md).
|
|
|
657
684
|
The work axis tracks every change being made to the project: new product
|
|
658
685
|
behavior, changes to its internals, or changes to how the project itself runs.
|
|
659
686
|
|
|
660
|
-
- **A work item is a folder that
|
|
661
|
-
(`docs/work/` unless the project says otherwise)
|
|
687
|
+
- **A work item is a folder that does not move when its stage changes.** It is
|
|
688
|
+
created in the work store (`docs/work/` unless the project says otherwise)
|
|
689
|
+
and stays there unless it is moved or renamed (`tcw work move`,
|
|
690
|
+
`tcw work rename`). Inside it is
|
|
662
691
|
one folder for each stage that produces something: `spec/spec.md`,
|
|
663
692
|
`implement/round-1.md`, and so on.
|
|
664
693
|
- **Every item has the same properties**: title, stage, priority, effort,
|
|
@@ -677,25 +706,25 @@ The full reference is [The Work component](docs/guide/work.md).
|
|
|
677
706
|
### Two backends, one model
|
|
678
707
|
|
|
679
708
|
A project keeps its work items with one of two **backends**, chosen by
|
|
680
|
-
`work.backend` in
|
|
709
|
+
`work.backend` in `.tcw/tcw-config.yaml`. The model is the same in both: the same
|
|
681
710
|
stages, the same properties, the same item folders and the same commands. What
|
|
682
711
|
differs is where each fact is kept.
|
|
683
712
|
|
|
684
|
-
| Fact | Filesystem | Jira
|
|
685
|
-
| -------------------------------------------- | ------------------------------ |
|
|
686
|
-
| the request | `request/request.md` | the ticket's description
|
|
687
|
-
| the stage | `item.yaml`
|
|
688
|
-
| assignee, priority, effort, complexity, tags | `item.yaml`
|
|
689
|
-
| parent and blocked-by | `item.yaml`
|
|
690
|
-
| comments | `comments/` in the item folder | the ticket's comments
|
|
691
|
-
| spec, plan, rounds, handoffs | the item folder | the item folder
|
|
692
|
-
| the records it changes, `capabilities.yaml` | the item folder | the item folder
|
|
693
|
-
| taxonomy and capabilities | the repository | the repository
|
|
713
|
+
| Fact | Filesystem | Jira |
|
|
714
|
+
| -------------------------------------------- | ------------------------------ | ------------------------------ |
|
|
715
|
+
| the request | `request/request.md` | the ticket's description |
|
|
716
|
+
| the stage | `tcw-work-item.yaml` | the ticket's status |
|
|
717
|
+
| assignee, priority, effort, complexity, tags | `tcw-work-item.yaml` | the ticket's fields and labels |
|
|
718
|
+
| parent and blocked-by | `tcw-work-item.yaml` | the ticket's parent and links |
|
|
719
|
+
| comments | `comments/` in the item folder | the ticket's comments |
|
|
720
|
+
| spec, plan, rounds, handoffs | the item folder | the item folder |
|
|
721
|
+
| the records it changes, `capabilities.yaml` | the item folder | the item folder |
|
|
722
|
+
| taxonomy and capabilities | the repository | the repository |
|
|
694
723
|
|
|
695
724
|
#### Filesystem: everything in the repository
|
|
696
725
|
|
|
697
726
|
With the **filesystem** backend, the default, everything about an item is a file
|
|
698
|
-
in your repository: its properties in `item.yaml`, its request in
|
|
727
|
+
in your repository: its properties in `tcw-work-item.yaml`, its request in
|
|
699
728
|
`request/request.md`, each comment in `comments/`, and its documents in its
|
|
700
729
|
stage folders. No other service is involved, and anything you can do to a file
|
|
701
730
|
(review it, diff it, grep it) you can do to your work items. See
|
|
@@ -761,18 +790,18 @@ flowchart LR
|
|
|
761
790
|
Dashed boxes are stages a project can turn off; an item then moves straight
|
|
762
791
|
past them. Any item can be moved to `discarded`, with a reason.
|
|
763
792
|
|
|
764
|
-
| Stage | Purpose
|
|
765
|
-
| ------------ |
|
|
766
|
-
| `inbox` | a raw request waits to be taken on
|
|
767
|
-
| `request` | what is asked for, and why
|
|
768
|
-
| `spec` | what to build, with acceptance criteria
|
|
769
|
-
| `plan` | how to build it, as ordered tasks
|
|
770
|
-
| `implement` | build it, and change the records
|
|
771
|
-
| `review` | check the change against the spec and plan
|
|
772
|
-
| `qa` | check the product's behavior against the request
|
|
773
|
-
| `completed` | finished work
|
|
774
|
-
| `discarded` | abandoned work, with the reason
|
|
775
|
-
| `postmortem` | for a finished item: which stage could first have caught a problem | `postmortem/postmortem.md`
|
|
793
|
+
| Stage | Purpose | Writes | Can be turned off |
|
|
794
|
+
| ------------ | ------------------------------------------------------------------ | ---------------------------------------- | ----------------- |
|
|
795
|
+
| `inbox` | a raw request waits to be taken on | nothing | no |
|
|
796
|
+
| `request` | what is asked for, and why | `request/request.md` (Jira: the ticket) | no |
|
|
797
|
+
| `spec` | what to build, with acceptance criteria | `spec/spec.md`, and `capabilities.yaml` | yes |
|
|
798
|
+
| `plan` | how to build it, as ordered tasks | `plan/plan.md` | yes |
|
|
799
|
+
| `implement` | build it, and change the records | `implement/round-N.md`, one per attempt | no |
|
|
800
|
+
| `review` | check the change against the spec and plan | `review/round-N.md`, each with a verdict | yes |
|
|
801
|
+
| `qa` | check the product's behavior against the request | `qa/round-N.md` (Jira: the ticket) | yes |
|
|
802
|
+
| `completed` | finished work | nothing | no |
|
|
803
|
+
| `discarded` | abandoned work, with the reason | nothing | no |
|
|
804
|
+
| `postmortem` | for a finished item: which stage could first have caught a problem | `postmortem/postmortem.md` | yes |
|
|
776
805
|
|
|
777
806
|
A project attaches its own text to a stage's instructions, its own checks before
|
|
778
807
|
an item moves into a stage, and its own commands after; see
|
|
@@ -806,10 +835,10 @@ The details are in [The Work component](docs/guide/work.md#moving-an-item).
|
|
|
806
835
|
|
|
807
836
|
#### Skills
|
|
808
837
|
|
|
809
|
-
| Skill | What it does
|
|
810
|
-
| -------------------------------------------- |
|
|
811
|
-
| [`work`](skills/work/SKILL.md) | Guides an agent through every stage of an item: deciding on an inbox arrival, writing the request, spec and plan, implementing, reviewing and testing, splitting large items, and
|
|
812
|
-
| [`work-create`](skills/work-create/SKILL.md) | Turns an idea for a piece of work into a work item, or adds it to the item that already covers it, after checking what is already tracked.
|
|
838
|
+
| Skill | What it does |
|
|
839
|
+
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
840
|
+
| [`work`](skills/work/SKILL.md) | Guides an agent through every stage of an item: deciding on an inbox arrival, writing the request, spec and plan, implementing, reviewing and testing, splitting large items, and making an epic's parts in other projects. |
|
|
841
|
+
| [`work-create`](skills/work-create/SKILL.md) | Turns an idea for a piece of work into a work item, or adds it to the item that already covers it, after checking what is already tracked. |
|
|
813
842
|
|
|
814
843
|
Most day-to-day work starts from one of the command skills (planning an item,
|
|
815
844
|
driving it to completion, processing the inbox) described in
|
|
@@ -819,44 +848,45 @@ driving it to completion, processing the inbox) described in
|
|
|
819
848
|
|
|
820
849
|
**Items**
|
|
821
850
|
|
|
822
|
-
| Command | What it does
|
|
823
|
-
| ------------------ |
|
|
824
|
-
| `tcw work new` | creates an item and prints its
|
|
825
|
-
| `tcw work list` | prints the
|
|
826
|
-
| `tcw work show` | prints an item's properties, its request and its comments
|
|
827
|
-
| `tcw work path` | prints the work store's folder, an item's folder, or where a stage's file goes
|
|
828
|
-
| `tcw work edit` | changes an item's properties
|
|
829
|
-
| `tcw work comment` | adds a comment, from standard input
|
|
830
|
-
| `tcw work rename` | renames an item's folder
|
|
831
|
-
| `tcw work
|
|
851
|
+
| Command | What it does |
|
|
852
|
+
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
853
|
+
| `tcw work new` | creates an item and prints its full identifier; its request from standard input; `--parent <epic>` puts it inside its parent's folder, `--flat` keeps it at the top; `tcw -C <folder> work new` creates it in another project |
|
|
854
|
+
| `tcw work list` | prints the full identifiers of this project's unfinished items; `--all` adds finished ones, `--scope` adds related projects' |
|
|
855
|
+
| `tcw work show` | prints an item's properties, its request and its comments |
|
|
856
|
+
| `tcw work path` | prints the work store's folder, an item's folder, or where a stage's file goes |
|
|
857
|
+
| `tcw work edit` | changes an item's properties |
|
|
858
|
+
| `tcw work comment` | adds a comment, from standard input |
|
|
859
|
+
| `tcw work rename` | renames an item's folder |
|
|
860
|
+
| `tcw work move` | moves an item's folder into another item's folder (`--into`) or to the top of the store (`--top`) |
|
|
861
|
+
| `tcw work tags` | lists, adds or removes the project's registered tags |
|
|
832
862
|
|
|
833
863
|
**Moving items**
|
|
834
864
|
|
|
835
|
-
| Command | What it does
|
|
836
|
-
| ------------------ |
|
|
865
|
+
| Command | What it does |
|
|
866
|
+
| ------------------ | ----------------------------------------------------------- |
|
|
837
867
|
| `tcw work advance` | moves an item to its next stage, or to the one `--to` names |
|
|
838
|
-
| `tcw work discard` | abandons an item, with a reason
|
|
868
|
+
| `tcw work discard` | abandons an item, with a reason |
|
|
839
869
|
|
|
840
870
|
**Stage instructions**
|
|
841
871
|
|
|
842
|
-
| Command
|
|
843
|
-
|
|
|
844
|
-
| `tcw work stage prompt`
|
|
845
|
-
| `tcw work lifecycle`
|
|
846
|
-
| `tcw work procedure`
|
|
847
|
-
| `tcw work docs`
|
|
872
|
+
| Command | What it does |
|
|
873
|
+
| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
|
|
874
|
+
| `tcw work stage prompt` | prints a stage's instructions, with this project's own text, for one item |
|
|
875
|
+
| `tcw work lifecycle` | prints every stage, whether it is turned on, and what this project attaches to it |
|
|
876
|
+
| `tcw work procedure` | prints one of TCW's procedures, such as `unattended-work` or `search`, with this project's own text for it |
|
|
877
|
+
| `tcw work docs` | prints the project's documentation entries: which documents a change must keep up to date |
|
|
848
878
|
|
|
849
879
|
**Jira**
|
|
850
880
|
|
|
851
|
-
| Command
|
|
852
|
-
|
|
|
853
|
-
| `tcw work tickets list`
|
|
854
|
-
| `tcw work tickets adopt` | makes a Jira ticket an item
|
|
881
|
+
| Command | What it does |
|
|
882
|
+
| ------------------------ | ----------------------------------------------- |
|
|
883
|
+
| `tcw work tickets list` | prints the Jira tickets waiting to become items |
|
|
884
|
+
| `tcw work tickets adopt` | makes a Jira ticket an item |
|
|
855
885
|
|
|
856
886
|
A session with the **filesystem** backend:
|
|
857
887
|
|
|
858
888
|
```sh
|
|
859
|
-
tcw work new "Export invoices as PDF" < request.md # → my-app/2026-09-15-export-invoices-as-pdf
|
|
889
|
+
tcw work new "Export invoices as PDF" < request.md # → my-app.work/2026-09-15-export-invoices-as-pdf
|
|
860
890
|
tcw work stage prompt spec 2026-09-15-export-invoices-as-pdf
|
|
861
891
|
tcw work advance 2026-09-15-export-invoices-as-pdf # request → spec
|
|
862
892
|
tcw work list --stage implement
|
|
@@ -867,7 +897,7 @@ A session with the **Jira** backend:
|
|
|
867
897
|
|
|
868
898
|
```sh
|
|
869
899
|
tcw work tickets list # SHOP-42
|
|
870
|
-
tcw work tickets adopt SHOP-42 # → shop/SHOP-42-export-invoices-as-pdf
|
|
900
|
+
tcw work tickets adopt SHOP-42 # → shop.work/SHOP-42-export-invoices-as-pdf
|
|
871
901
|
tcw work advance SHOP-42 # request → spec; the ticket moves to the status set for spec
|
|
872
902
|
tcw work show SHOP-42
|
|
873
903
|
```
|
|
@@ -890,36 +920,36 @@ across the axes.
|
|
|
890
920
|
|
|
891
921
|
**Setting up and configuring**
|
|
892
922
|
|
|
893
|
-
| Skill | What it does
|
|
894
|
-
| ---------------------------------------------------------- |
|
|
895
|
-
| [`setup`](skills/setup/SKILL.md) | Gets TCW working: installs or repairs the CLI, starts using TCW in a repository, connects a project to Jira, sets up a project on a new machine, and drafts a first taxonomy or capabilities list from existing code.
|
|
923
|
+
| Skill | What it does |
|
|
924
|
+
| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
925
|
+
| [`setup`](skills/setup/SKILL.md) | Gets TCW working: installs or repairs the CLI, starts using TCW in a repository, connects a project to Jira, sets up a project on a new machine, and drafts a first taxonomy or capabilities list from existing code. |
|
|
896
926
|
| [`configure`](skills/configure/SKILL.md) | Changes a working project's configuration: which stages it uses, the text and commands bound to each, the Jira backend, documentation entries, where stores live, connected and inherited projects, and personal configuration. |
|
|
897
|
-
| [`documentation-sync`](skills/documentation-sync/SKILL.md) | Decides which documents a finished change must update (README, changelogs, release notes, guides, skills), and runs the version cut when you ask for one.
|
|
927
|
+
| [`documentation-sync`](skills/documentation-sync/SKILL.md) | Decides which documents a finished change must update (README, changelogs, release notes, guides, skills), and runs the version cut when you ask for one. |
|
|
898
928
|
|
|
899
929
|
**Command skills: the everyday workflows**
|
|
900
930
|
|
|
901
|
-
| Skill | What it does
|
|
902
|
-
| ---------------------------------------------------------------------------------------- |
|
|
903
|
-
| [`commands-process-inbox`](skills/commands-process-inbox/SKILL.md) | Decides on every arrival in the work inbox, then writes the request for each one taken on.
|
|
904
|
-
| [`commands-plan-work`](skills/commands-plan-work/SKILL.md) | Takes an item, or a request made in chat, through the request, spec and plan stages, and stops before any code.
|
|
931
|
+
| Skill | What it does |
|
|
932
|
+
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
933
|
+
| [`commands-process-inbox`](skills/commands-process-inbox/SKILL.md) | Decides on every arrival in the work inbox, then writes the request for each one taken on. |
|
|
934
|
+
| [`commands-plan-work`](skills/commands-plan-work/SKILL.md) | Takes an item, or a request made in chat, through the request, spec and plan stages, and stops before any code. |
|
|
905
935
|
| [`commands-drive-work-to-completion`](skills/commands-drive-work-to-completion/SKILL.md) | Takes an item from wherever it is through implement, review and qa, to completed where the agent may record the qa verdict, or to qa for a person where it may not. |
|
|
906
|
-
| [`commands-pause-work`](skills/commands-pause-work/SKILL.md) | Stops the work in hand, writes down what resuming needs in the item, and waits for you to say carry on.
|
|
936
|
+
| [`commands-pause-work`](skills/commands-pause-work/SKILL.md) | Stops the work in hand, writes down what resuming needs in the item, and waits for you to say carry on. |
|
|
907
937
|
|
|
908
938
|
**Extras: optional, built for one way of working**
|
|
909
939
|
|
|
910
|
-
| Skill | What it does
|
|
911
|
-
| ------------------------------------------------------------------ |
|
|
940
|
+
| Skill | What it does |
|
|
941
|
+
| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
912
942
|
| [`extras-autonomous-work`](skills/extras-autonomous-work/SKILL.md) | Drives work items to completion unattended, asking read-only advisors wherever the lifecycle would ask you: by default Codex and a read-only subagent, replaceable by your project. |
|
|
913
|
-
| [`extras-triage-issues`](skills/extras-triage-issues/SKILL.md) | Works through **your** project's GitHub issues and turns the ones worth doing into work items.
|
|
914
|
-
| [`extras-report`](skills/extras-report/SKILL.md) | Files a bug report or suggestion about TCW itself on [this project's issues](https://github.com/brocef/TCW/issues).
|
|
943
|
+
| [`extras-triage-issues`](skills/extras-triage-issues/SKILL.md) | Works through **your** project's GitHub issues and turns the ones worth doing into work items. |
|
|
944
|
+
| [`extras-report`](skills/extras-report/SKILL.md) | Files a bug report or suggestion about TCW itself on [this project's issues](https://github.com/brocef/TCW/issues). |
|
|
915
945
|
|
|
916
946
|
**Agents.** Two read-only agents ship with the plugin. Neither edits a file or
|
|
917
947
|
moves an item; each reports back to the session that started it.
|
|
918
948
|
|
|
919
|
-
| Agent | What it does
|
|
920
|
-
| ----------------- |
|
|
949
|
+
| Agent | What it does |
|
|
950
|
+
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
921
951
|
| `reviewer` | For the `review` stage: reads an item's change against its spec, plan and `capabilities.yaml`, runs the project's checks, and recommends a verdict criterion by criterion; the session that started it writes the round. |
|
|
922
|
-
| `backlog-auditor` | Checks one unfinished item against your project's audit-backlog procedure, `tcw work procedure audit-backlog`, checking the item's claims against the code.
|
|
952
|
+
| `backlog-auditor` | Checks one unfinished item against your project's audit-backlog procedure, `tcw work procedure audit-backlog`, checking the item's claims against the code. |
|
|
923
953
|
|
|
924
954
|
## TCW Local Web App
|
|
925
955
|
|
|
@@ -941,7 +971,7 @@ tcw serve --port 9000 # use a different port
|
|
|
941
971
|
document is a link to its target.
|
|
942
972
|
- **What you can change.** An item's documents, rounds and handoffs, its
|
|
943
973
|
`capabilities.yaml`, its properties and comments; new work items, in this
|
|
944
|
-
project or in a
|
|
974
|
+
project or in a related one; and taxonomy entries and capabilities, created
|
|
945
975
|
and edited.
|
|
946
976
|
- **No stage moves.** The app shows each item's stage but never changes it, and
|
|
947
977
|
names the `tcw work advance` command to run instead.
|
|
@@ -960,20 +990,20 @@ Everything else about the app is in
|
|
|
960
990
|
|
|
961
991
|
## Documentation
|
|
962
992
|
|
|
963
|
-
| Document
|
|
964
|
-
|
|
|
965
|
-
| [The Work component](docs/guide/work.md)
|
|
966
|
-
| [Using TCW with Jira](docs/guide/jira.md)
|
|
967
|
-
| [Configuration](docs/guide/configuration.md)
|
|
968
|
-
| [The command line](docs/guide/cli.md)
|
|
969
|
-
| [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md)
|
|
970
|
-
| [
|
|
971
|
-
| [Linking and validation](docs/guide/linking-and-validation.md)
|
|
972
|
-
| [The local web viewer](docs/guide/web-viewer.md)
|
|
973
|
-
| [Configuration reference](skills/configure/SKILL.md)
|
|
974
|
-
| [The abstraction rules](docs/lifecycle/abstraction.md)
|
|
975
|
-
| [Release notes](docs/release-notes/)
|
|
976
|
-
| Migration guides
|
|
993
|
+
| Document | Covers |
|
|
994
|
+
| -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
995
|
+
| [The Work component](docs/guide/work.md) | Work items, their stages and folders, nesting, renaming and moving items, and every `tcw work` command, for both backends |
|
|
996
|
+
| [Using TCW with Jira](docs/guide/jira.md) | The Jira backend: who owns what, writing and following tickets, setting up, statuses, adopting tickets, QA on the ticket |
|
|
997
|
+
| [Configuration](docs/guide/configuration.md) | `.tcw/tcw-config.yaml`: what a parent passes down, personal configuration and environment variables, stage bindings, how hooks run, documentation entries, and the opt-in git example |
|
|
998
|
+
| [The command line](docs/guide/cli.md) | What every command prints on standard output and standard error, `--scope`, `--project` and `-C`, full identifiers, and the exit codes |
|
|
999
|
+
| [Taxonomy and Capabilities](docs/guide/taxonomy-and-capabilities.md) | Declaring vocabulary, features and capabilities, from a request to the records, renaming and moving them, drift, and inheriting and overriding both |
|
|
1000
|
+
| [Related projects](docs/guide/multi-repo.md) | Parents and children, manifests, finding a related project, working in another project with `-C`, stores in another repository, and `tcw project provision` |
|
|
1001
|
+
| [Linking and validation](docs/guide/linking-and-validation.md) | `tcw://` references between objects, and `tcw validate` as a CI check |
|
|
1002
|
+
| [The local web viewer](docs/guide/web-viewer.md) | Everything about `tcw serve` |
|
|
1003
|
+
| [Configuration reference](skills/configure/SKILL.md) | Every configuration key, and which ones a person may override |
|
|
1004
|
+
| [The abstraction rules](docs/lifecycle/abstraction.md) | Why every operation must work for a backend that is not a filesystem, in full |
|
|
1005
|
+
| [Release notes](docs/release-notes/) | What changed for users in each version |
|
|
1006
|
+
| Migration guides | Upgrading across a breaking release: [3.x → 4.0](docs/migration-guide-3.X-to-4.0.0.md), [0.10 → 0.11](docs/migration-guide-0.10.X-to-0.11.0.md), [0.12 → 0.13](docs/migration-guide-0.12.X-to-0.13.0.md), [0.14 → 0.15](docs/migration-guide-0.14.X-to-0.15.0.md), [0.15 → 0.16](docs/migration-guide-0.15.X-to-0.16.0.md), [0.21 → 1.0](docs/migration-guide-0.21.X-to-1.0.0.md), [1.x → 2.0](docs/migration-guide-1.X-to-2.0.0.md), [2.4 → 2.5](docs/migration-guide-2.4.X-to-2.5.0.md), [2.8 → 3.0](docs/migration-guide-2.8-to-3.0.0.md) |
|
|
977
1007
|
|
|
978
1008
|
Every command also has `--help`.
|
|
979
1009
|
|