formist-cli 0.1.1__tar.gz → 0.2.1__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.
- formist_cli-0.2.1/.claude-plugin/plugin.json +9 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/PKG-INFO +54 -4
- {formist_cli-0.1.1 → formist_cli-0.2.1}/README.ar.md +52 -3
- {formist_cli-0.1.1 → formist_cli-0.2.1}/README.fr.md +58 -5
- {formist_cli-0.1.1 → formist_cli-0.2.1}/README.md +53 -3
- {formist_cli-0.1.1 → formist_cli-0.2.1}/README.zh-CN.md +52 -7
- formist_cli-0.2.1/hooks/hooks.json +10 -0
- formist_cli-0.2.1/monitors/monitors.json +7 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/pyproject.toml +1 -1
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/cli.py +398 -80
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/cli_support.py +19 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/connectors.py +22 -5
- formist_cli-0.2.1/src/formist_cli/plugin_hooks.py +239 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/privileges.py +71 -51
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/projects.py +7 -3
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/skills.py +8 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/spaces.py +41 -2
- formist_cli-0.2.1/src/formist_cli/task_archive.py +277 -0
- formist_cli-0.2.1/src/formist_cli/task_assignee.py +34 -0
- formist_cli-0.2.1/src/formist_cli/task_attach.py +102 -0
- formist_cli-0.2.1/src/formist_cli/task_check.py +261 -0
- formist_cli-0.2.1/src/formist_cli/task_cloud.py +570 -0
- formist_cli-0.2.1/src/formist_cli/task_duration.py +73 -0
- formist_cli-0.2.1/src/formist_cli/task_filter.py +87 -0
- formist_cli-0.2.1/src/formist_cli/task_format.py +90 -0
- formist_cli-0.2.1/src/formist_cli/task_fuzzy_date.py +432 -0
- formist_cli-0.2.1/src/formist_cli/task_identity.py +63 -0
- formist_cli-0.2.1/src/formist_cli/task_import.py +301 -0
- formist_cli-0.2.1/src/formist_cli/task_intake.py +55 -0
- formist_cli-0.2.1/src/formist_cli/task_json.py +233 -0
- formist_cli-0.2.1/src/formist_cli/task_lock.py +65 -0
- formist_cli-0.2.1/src/formist_cli/task_mirror.py +158 -0
- formist_cli-0.2.1/src/formist_cli/task_model.py +230 -0
- formist_cli-0.2.1/src/formist_cli/task_monitor.py +353 -0
- formist_cli-0.2.1/src/formist_cli/task_parse.py +657 -0
- formist_cli-0.2.1/src/formist_cli/task_paths.py +191 -0
- formist_cli-0.2.1/src/formist_cli/task_project.py +78 -0
- formist_cli-0.2.1/src/formist_cli/task_questions.py +181 -0
- formist_cli-0.2.1/src/formist_cli/task_queue.py +95 -0
- formist_cli-0.2.1/src/formist_cli/task_ref.py +72 -0
- formist_cli-0.2.1/src/formist_cli/task_search.py +24 -0
- formist_cli-0.2.1/src/formist_cli/task_serialize.py +344 -0
- formist_cli-0.2.1/src/formist_cli/task_sessions.py +225 -0
- formist_cli-0.2.1/src/formist_cli/task_status.py +133 -0
- formist_cli-0.2.1/src/formist_cli/task_store.py +1370 -0
- formist_cli-0.2.1/src/formist_cli/task_title.py +29 -0
- formist_cli-0.2.1/src/formist_cli/task_views.py +418 -0
- formist_cli-0.2.1/src/formist_cli/task_width.py +21 -0
- formist_cli-0.2.1/src/formist_cli/task_yaml.py +361 -0
- formist_cli-0.2.1/src/formist_cli/tasks.py +1750 -0
- formist_cli-0.2.1/src/formist_cli/workflow_corpus.py +27 -0
- formist_cli-0.2.1/src/formist_cli/workflow_golden.json +41 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/1-plain-task-example.md +22 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/10-title-with-colon-and.md +22 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/2-decision-with-two-op.md +40 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/4-a-brief-for-ai.md +13 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/6-a-milestone.md +12 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/7-node-with-sub-questi.md +27 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/8-needs-acceptance.md +34 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/active/9-dependent-node.md +13 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/archived/3-fyi-entry.md +12 -0
- formist_cli-0.2.1/tests/fixtures/task_decisions/archived/5-for-the-owner.md +13 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_admin_flag_gate.py +76 -10
- formist_cli-0.2.1/tests/test_chat_group.py +99 -0
- formist_cli-0.2.1/tests/test_connector_group.py +94 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_context.py +8 -4
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_login.py +12 -5
- formist_cli-0.2.1/tests/test_moved_to_fmdev.py +129 -0
- formist_cli-0.2.1/tests/test_plugin_hooks.py +195 -0
- formist_cli-0.2.1/tests/test_plugin_manifest.py +66 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_privileges.py +16 -7
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_settings.py +21 -7
- formist_cli-0.2.1/tests/test_skill_group.py +126 -0
- formist_cli-0.2.1/tests/test_spaces_set_logo.py +96 -0
- formist_cli-0.2.1/tests/test_task_archive_read_only.py +246 -0
- formist_cli-0.2.1/tests/test_task_check.py +289 -0
- formist_cli-0.2.1/tests/test_task_cli.py +839 -0
- formist_cli-0.2.1/tests/test_task_cloud.py +638 -0
- formist_cli-0.2.1/tests/test_task_fuzzy_date.py +84 -0
- formist_cli-0.2.1/tests/test_task_import.py +102 -0
- formist_cli-0.2.1/tests/test_task_import_archive.py +325 -0
- formist_cli-0.2.1/tests/test_task_mirror.py +83 -0
- formist_cli-0.2.1/tests/test_task_monitor.py +161 -0
- formist_cli-0.2.1/tests/test_task_nod_interop.py +289 -0
- formist_cli-0.2.1/tests/test_task_parse_serialize.py +130 -0
- formist_cli-0.2.1/tests/test_task_ref.py +17 -0
- formist_cli-0.2.1/tests/test_task_sessions.py +177 -0
- formist_cli-0.2.1/tests/test_task_store.py +399 -0
- formist_cli-0.2.1/tests/test_task_views.py +132 -0
- formist_cli-0.2.1/tests/test_task_workflow_parity.py +213 -0
- formist_cli-0.2.1/tests/test_task_yaml.py +84 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/uv.lock +1 -1
- {formist_cli-0.1.1 → formist_cli-0.2.1}/.github/workflows/release.yml +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/.github/workflows/test.yml +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/.gitignore +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/LICENSE +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/docs/screenshot.png +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/docs/screenshot.svg +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/scripts/render_screenshot.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/__init__.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/__main__.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/airtable.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/alerts.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/api.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/chat.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/chats.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/context.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/diff.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/doctor.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/export.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/files.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/importer.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/kb.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/login.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/logs.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/meetings.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/messages.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/participants.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/prefs.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/resolve.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/settings.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/skill_library.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/space_plan.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/targets.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/textnorm.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/tokens.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/update.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/uploads.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/usage_tokens.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/users.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/src/formist_cli/whatsapp.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_airtable.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_alerts.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_api_and_tokens.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_api_uploads_transport.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_audit_log_shows_the_newest.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_chat.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_chat_message.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_chats.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_cli_registration_is_unique.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_connector_ops.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_connectors.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_diff.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_doctor.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_export.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_files.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_files_download.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_files_merge.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_grants_render.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_help_matches_the_write_guard.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_importer.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_kb.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_logs.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_meetings.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_messages.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_participants.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_prefs.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_projects.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_proposals.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_render_screenshot.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_report_provenance.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_resolve.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_skill_library_install.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_skills.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_space_plan.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_spaces.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_stream_transport.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_targets.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_update.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_upload_dir.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_uploads.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_usage_tokens.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_users.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_users_writes.py +0 -0
- {formist_cli-0.1.1 → formist_cli-0.2.1}/tests/test_whatsapp.py +0 -0
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "fm-task",
|
|
3
|
+
"displayName": "fm task",
|
|
4
|
+
"version": "0.1.0",
|
|
5
|
+
"description": "fm task is the AI's task and decision hub: injects usage rules and open work at session start, reminds the model to log the owner's words when they name a node, and keeps a monitor running against the current decisions/ directory (local mode) or Formist space (cloud mode, C1053/C1139).",
|
|
6
|
+
"author": { "name": "WeCarbon" },
|
|
7
|
+
"license": "MIT",
|
|
8
|
+
"repository": "https://github.com/WeCarbon/formist-cli"
|
|
9
|
+
}
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: formist-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.2.1
|
|
4
4
|
Summary: Command-line client for Formist and Evane deployments
|
|
5
5
|
Project-URL: Homepage, https://formist.ai
|
|
6
6
|
Project-URL: Repository, https://github.com/WeCarbon/formist-cli
|
|
@@ -49,8 +49,8 @@ changes data always shows what it would do first; committing is a separate, expl
|
|
|
49
49
|
and where each came from, a flag, a remembered default, or nothing, so a wrong target is caught
|
|
50
50
|
by reading the screen, not by its effect.
|
|
51
51
|
- **Dry run by default.** A command that changes data prints what it would do and waits for
|
|
52
|
-
`--apply`. `fm
|
|
53
|
-
matches before committing, so a stale read can't turn into a wrong write.
|
|
52
|
+
`--apply`. `fm participants dedupe`, which merges a group of duplicate rows, re-checks the plan
|
|
53
|
+
still matches before committing, so a stale read can't turn into a wrong write.
|
|
54
54
|
- **A credential per deployment.** `fm login` stores an OAuth credential at `0600`, one file per
|
|
55
55
|
host, so signing in to a staging deployment never touches production. `FORMIST_TOKEN` supplies
|
|
56
56
|
one for CI: used as-is, never written to disk, never refreshed.
|
|
@@ -116,7 +116,7 @@ remembered host: name it with `--host`, or the default (`formist`) is used.
|
|
|
116
116
|
### Writes
|
|
117
117
|
|
|
118
118
|
Most commands that change data run as a dry run first and print what they would do; add
|
|
119
|
-
`--apply` to commit. `fm
|
|
119
|
+
`--apply` to commit. `fm participants dedupe`, which merges a group of duplicate rows, is slightly
|
|
120
120
|
different: the dry run prints a plan token, and `--apply <token>` re-runs the dry run to confirm
|
|
121
121
|
the plan still matches before committing. A handful of actions with no undo, such as `fm spaces
|
|
122
122
|
--admin delete`, have no dry run at all and say so in their own `--help`.
|
|
@@ -131,6 +131,56 @@ needs no login, `fm doctor` rolls health up across every deployment, and the res
|
|
|
131
131
|
`skill-library-install`, `meeting`, `project`, `connector`, `skills-add`, `skills-update`,
|
|
132
132
|
`proposals`, `audit-log`, `connectors`, `files`, read or write your own space the same way.
|
|
133
133
|
|
|
134
|
+
### Tasks (`fm task`)
|
|
135
|
+
|
|
136
|
+
`fm task` is a built-in port of [`nod`](https://github.com/wecarbon/noddit)'s task-and-decision
|
|
137
|
+
tracker: a node is one piece of work, a task when an AI can just do it, a decision when the
|
|
138
|
+
owner has to rule on it. It runs in one of two modes:
|
|
139
|
+
|
|
140
|
+
- **Logged out**, in any project: `fm task init` creates a `decisions/` folder, and every
|
|
141
|
+
command below finds it by walking up from the current directory, the same way `git` finds
|
|
142
|
+
`.git`. Nothing leaves the machine.
|
|
143
|
+
- **Logged in**, with `fm login`: `fm task --host <deployment>` (or a remembered `fm use` host
|
|
144
|
+
with a stored credential) talks to that space's node API instead, so a team shares one
|
|
145
|
+
tracker through Formist/Evane rather than a per-clone folder. Not every verb has a server
|
|
146
|
+
route yet; one that doesn't says so rather than guessing.
|
|
147
|
+
|
|
148
|
+
```sh
|
|
149
|
+
fm task init # creates decisions/ here
|
|
150
|
+
fm task add "Write the onboarding doc" --task # a new node
|
|
151
|
+
fm task start X1 # to do -> in progress
|
|
152
|
+
fm task note X1 "found last year's draft" # progress, without closing it
|
|
153
|
+
fm task show active # every open node (bare `show` lists only ones needing a decision)
|
|
154
|
+
fm task done X1 --note "doc is up" # -> done
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
A decision looks the same, just with options instead of `--task`:
|
|
158
|
+
|
|
159
|
+
```sh
|
|
160
|
+
fm task add "Which domain for staging" -o 1="api-staging.example.com" -o 2="staging-api.example.com"
|
|
161
|
+
fm task push X2 1 --note "matches the cert" # the owner's answer, recorded on the node
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
Every write needs an author: pass `--author "<you> · <doing what>"` or export `NODDIT_AUTHOR`
|
|
165
|
+
once per session. `fm task whoami` reports who a write would sign as: the signed-in account and
|
|
166
|
+
space once `fm login`/`--host` resolves to cloud mode, otherwise the local identity stamped on
|
|
167
|
+
each note. `fm task briefs` lists work the owner filed that nobody has picked up yet;
|
|
168
|
+
`fm task claim <ref>` takes one. Run `fm task --help` for the full verb list and `fm task <verb>
|
|
169
|
+
--help` for its flags.
|
|
170
|
+
|
|
171
|
+
#### Claude Code plugin
|
|
172
|
+
|
|
173
|
+
The git repo, not the `pipx` package, is also a Claude Code plugin: `hooks/hooks.json` injects
|
|
174
|
+
the `fm task` usage rules and the project's open nodes at the start of a session, and
|
|
175
|
+
`monitors/monitors.json` starts `fm task monitor --here` so the owner's replies reach the agent
|
|
176
|
+
without it polling. It isn't published to a marketplace, so load it from a clone instead of the
|
|
177
|
+
installed package:
|
|
178
|
+
|
|
179
|
+
```sh
|
|
180
|
+
git clone https://github.com/WeCarbon/formist-cli
|
|
181
|
+
claude --plugin-dir formist-cli
|
|
182
|
+
```
|
|
183
|
+
|
|
134
184
|
## FAQ
|
|
135
185
|
|
|
136
186
|
**Do I need platform-admin access to use this?**
|
|
@@ -35,8 +35,8 @@
|
|
|
35
35
|
قيمة: خيار، أو قيمة افتراضية محفوظة، أو لا شيء. يُكتشف الهدف الخاطئ بقراءة الشاشة، لا
|
|
36
36
|
بعد وقوع أثره.
|
|
37
37
|
- **تشغيل تجريبي افتراضيًا.** يعرض الأمر الذي يغيّر البيانات أولًا ما سيفعله وينتظر
|
|
38
|
-
`--apply`. أمر `fm
|
|
39
|
-
الخطة ما زالت مطابقة قبل التثبيت، حتى لا تتحول قراءة قديمة إلى كتابة خاطئة.
|
|
38
|
+
`--apply`. أمر `fm participants dedupe`، الذي يدمج مجموعة من السجلات المكرّرة، يعيد
|
|
39
|
+
التحقق من أن الخطة ما زالت مطابقة قبل التثبيت، حتى لا تتحول قراءة قديمة إلى كتابة خاطئة.
|
|
40
40
|
- **بيانات اعتماد لكل نشرة.** يخزّن `fm login` بيانات اعتماد OAuth بصلاحيات `0600`، ملف
|
|
41
41
|
لكل نشرة، فتسجيل الدخول إلى نشرة تجريبية لا يمس أبدًا بيانات الإنتاج. يوفّر
|
|
42
42
|
`FORMIST_TOKEN` بيانات اعتماد لبيئات التكامل المستمر: تُستخدم كما هي، ولا تُكتب على
|
|
@@ -105,7 +105,7 @@ fm kb search "venue contract" --space <space-id>
|
|
|
105
105
|
### الكتابة
|
|
106
106
|
|
|
107
107
|
تعمل معظم الأوامر التي تغيّر البيانات كتشغيل تجريبي أولًا وتطبع ما ستفعله؛ أضف `--apply`
|
|
108
|
-
للتثبيت. يختلف `fm
|
|
108
|
+
للتثبيت. يختلف `fm participants dedupe` قليلًا، فهو يدمج مجموعة من السجلات المكرّرة: يطبع
|
|
109
109
|
التشغيل التجريبي رمز خطة، ويعيد `--apply <الرمز>` تشغيل التجربة للتأكد من أن الخطة ما
|
|
110
110
|
زالت مطابقة قبل التثبيت. بعض الإجراءات التي لا رجعة فيها، مثل
|
|
111
111
|
`fm spaces --admin delete`، لا تشغيل تجريبي لها إطلاقًا، وتوضح ذلك في `--help` الخاصة بها.
|
|
@@ -121,6 +121,55 @@ fm kb search "venue contract" --space <space-id>
|
|
|
121
121
|
`project`، `connector`، `skills-add`، `skills-update`، `proposals`،
|
|
122
122
|
`audit-log`، `connectors`، `files`، تقرأ أو تكتب مساحتك بنفس الطريقة.
|
|
123
123
|
|
|
124
|
+
### المهام (`fm task`)
|
|
125
|
+
|
|
126
|
+
يضمّ `fm task` نسخة مدمجة من أداة تتبع المهام والقرارات في
|
|
127
|
+
[`nod`](https://github.com/wecarbon/noddit): العقدة هي وحدة عمل واحدة، مهمة إذا كان الوكيل
|
|
128
|
+
يستطيع تنفيذها مباشرة، وقرار إذا احتاجت رأي المسؤول أولًا. تعمل بإحدى طريقتين:
|
|
129
|
+
|
|
130
|
+
- **بلا تسجيل دخول**، في أي مشروع: يُنشئ `fm task init` مجلد `decisions/`، وكل أمر أدناه يجده
|
|
131
|
+
بالصعود من المجلد الحالي، بالطريقة نفسها التي يجد بها `git` مجلد `.git`. لا يُرسَل شيء إلى أي
|
|
132
|
+
مكان.
|
|
133
|
+
- **مع تسجيل الدخول**، عبر `fm login`: يتوجّه `fm task --host <النشرة>` (أو نشرة حفظها
|
|
134
|
+
`fm use` مع بيانات اعتماد مخزّنة) إلى واجهة عُقد تلك المساحة بدلًا من ذلك، فيشترك فريق في
|
|
135
|
+
أداة تتبع واحدة عبر Formist/Evane بدل مجلد لكل نسخة محلية. ليس لكل أمر فرعي مسار على الخادم
|
|
136
|
+
بعد؛ ما لا يملك مسارًا يقول ذلك مباشرة بدل التخمين.
|
|
137
|
+
|
|
138
|
+
```sh
|
|
139
|
+
fm task init # creates decisions/ here
|
|
140
|
+
fm task add "Write the onboarding doc" --task # a new node
|
|
141
|
+
fm task start X1 # to do -> in progress
|
|
142
|
+
fm task note X1 "found last year's draft" # progress, without closing it
|
|
143
|
+
fm task show active # every open node (bare `show` lists only ones needing a decision)
|
|
144
|
+
fm task done X1 --note "doc is up" # -> done
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
يبدو القرار بالشكل نفسه، باستبدال `--task` بخيارات:
|
|
148
|
+
|
|
149
|
+
```sh
|
|
150
|
+
fm task add "Which domain for staging" -o 1="api-staging.example.com" -o 2="staging-api.example.com"
|
|
151
|
+
fm task push X2 1 --note "matches the cert" # the owner's answer, recorded on the node
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
تحتاج كل عملية كتابة مؤلّفًا: مرّر `--author "<اسمك> · ما تفعله"`، أو صدّر `NODDIT_AUTHOR` مرة
|
|
155
|
+
واحدة لكل جلسة. يوضّح `fm task whoami` باسم من تُسجَّل الكتابة: الحساب والمساحة المتصلة متى
|
|
156
|
+
حلّ `fm login`/`--host` الوضع السحابي، وإلا فالهوية المحلية المطبوعة على كل ملاحظة. يسرد
|
|
157
|
+
`fm task briefs` الأعمال التي ملفها المسؤول ولم يأخذها أحد بعد؛ ويأخذ `fm task claim <ref>`
|
|
158
|
+
واحدة منها. شغّل `fm task --help` لقائمة الأوامر كاملة، و`fm task <command> --help` لخيارات
|
|
159
|
+
كل أمر.
|
|
160
|
+
|
|
161
|
+
#### إضافة Claude Code
|
|
162
|
+
|
|
163
|
+
مستودع git نفسه، لا حزمة `pipx`، هو أيضًا إضافة لـ Claude Code: يحقن `hooks/hooks.json` قواعد
|
|
164
|
+
استخدام `fm task` وعُقد المشروع غير المكتملة في بداية كل جلسة، ويشغّل `monitors/monitors.json`
|
|
165
|
+
أمر `fm task monitor --here` حتى تصل ردود المسؤول إلى الوكيل دون أن يستطلعها بنفسه. لم تُنشر
|
|
166
|
+
هذه الإضافة في أي سوق إضافات، فحمّلها من نسخة مستودع بدلًا من الحزمة المثبَّتة:
|
|
167
|
+
|
|
168
|
+
```sh
|
|
169
|
+
git clone https://github.com/WeCarbon/formist-cli
|
|
170
|
+
claude --plugin-dir formist-cli
|
|
171
|
+
```
|
|
172
|
+
|
|
124
173
|
## الأسئلة الشائعة
|
|
125
174
|
|
|
126
175
|
**هل أحتاج صلاحية إدارة المنصة لاستخدام هذه الأداة؟**
|
|
@@ -36,9 +36,9 @@ données montre toujours d'abord ce qu'elle ferait ; valider est une étape à p
|
|
|
36
36
|
a résolus, et d'où ils viennent : une option, une valeur par défaut mémorisée, ou rien du
|
|
37
37
|
tout. Une mauvaise cible se repère en lisant l'écran, pas par ses conséquences.
|
|
38
38
|
- **Simulation par défaut.** Une commande qui modifie des données affiche d'abord ce qu'elle
|
|
39
|
-
ferait et attend `--apply`. `fm
|
|
40
|
-
revérifie que le plan correspond toujours avant de valider, pour qu'une lecture
|
|
41
|
-
devienne jamais une écriture erronée.
|
|
39
|
+
ferait et attend `--apply`. `fm participants dedupe`, qui fusionne un groupe de lignes en
|
|
40
|
+
double, revérifie que le plan correspond toujours avant de valider, pour qu'une lecture
|
|
41
|
+
périmée ne devienne jamais une écriture erronée.
|
|
42
42
|
- **Un identifiant par déploiement.** `fm login` enregistre un identifiant OAuth avec les
|
|
43
43
|
droits `0600`, un fichier par déploiement, de sorte que se connecter à un environnement de
|
|
44
44
|
test ne touche jamais la production. `FORMIST_TOKEN` en fournit un pour la CI : utilisé tel
|
|
@@ -109,8 +109,8 @@ valeur par défaut (`formist`) est utilisée.
|
|
|
109
109
|
### Écritures
|
|
110
110
|
|
|
111
111
|
La plupart des commandes qui modifient des données s'exécutent d'abord en simulation et
|
|
112
|
-
affichent ce qu'elles feraient ; ajoutez `--apply` pour valider. `fm
|
|
113
|
-
|
|
112
|
+
affichent ce qu'elles feraient ; ajoutez `--apply` pour valider. `fm participants dedupe`, qui
|
|
113
|
+
fusionne un groupe de lignes en double, fonctionne un peu différemment : la simulation
|
|
114
114
|
affiche un jeton de plan, et `--apply <jeton>` relance la simulation pour confirmer que le plan
|
|
115
115
|
correspond toujours avant de valider. Quelques actions irréversibles, comme
|
|
116
116
|
`fm spaces --admin delete`, n'ont aucune simulation et le précisent dans leur propre `--help`.
|
|
@@ -126,6 +126,59 @@ l'état de santé sur chaque déploiement, et le reste, `chats`, `chat`, `kb`, `
|
|
|
126
126
|
`meeting`, `project`, `connector`, `skills-add`, `skills-update`, `proposals`, `audit-log`,
|
|
127
127
|
`connectors`, `files`, lit ou écrit votre propre espace de la même façon.
|
|
128
128
|
|
|
129
|
+
### Tâches (`fm task`)
|
|
130
|
+
|
|
131
|
+
`fm task` est un portage intégré du suivi des tâches et décisions de
|
|
132
|
+
[`nod`](https://github.com/wecarbon/noddit) : un nœud est une unité de travail, une tâche quand
|
|
133
|
+
un agent peut simplement la faire, une décision quand le responsable doit d'abord trancher. Il
|
|
134
|
+
fonctionne selon deux modes :
|
|
135
|
+
|
|
136
|
+
- **Déconnecté**, dans n'importe quel projet : `fm task init` crée un dossier `decisions/`, et
|
|
137
|
+
chaque commande ci-dessous le retrouve en remontant depuis le répertoire courant, comme `git`
|
|
138
|
+
retrouve `.git`. Rien ne quitte la machine.
|
|
139
|
+
- **Connecté**, avec `fm login` : `fm task --host <déploiement>` (ou un déploiement mémorisé par
|
|
140
|
+
`fm use` avec un identifiant stocké) s'adresse à l'API de nœuds de cet espace à la place, pour
|
|
141
|
+
qu'une équipe partage un seul suivi via Formist/Evane plutôt qu'un dossier par clone. Toutes
|
|
142
|
+
les commandes n'ont pas encore de route côté serveur ; celles qui n'en ont pas le disent
|
|
143
|
+
plutôt que de deviner.
|
|
144
|
+
|
|
145
|
+
```sh
|
|
146
|
+
fm task init # creates decisions/ here
|
|
147
|
+
fm task add "Write the onboarding doc" --task # a new node
|
|
148
|
+
fm task start X1 # to do -> in progress
|
|
149
|
+
fm task note X1 "found last year's draft" # progress, without closing it
|
|
150
|
+
fm task show active # every open node (bare `show` lists only ones needing a decision)
|
|
151
|
+
fm task done X1 --note "doc is up" # -> done
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
Une décision ressemble à la même chose, avec des options à la place de `--task` :
|
|
155
|
+
|
|
156
|
+
```sh
|
|
157
|
+
fm task add "Which domain for staging" -o 1="api-staging.example.com" -o 2="staging-api.example.com"
|
|
158
|
+
fm task push X2 1 --note "matches the cert" # the owner's answer, recorded on the node
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
Chaque écriture a besoin d'un auteur : passez `--author "<vous> · <ce que vous faites>"`, ou
|
|
162
|
+
exportez `NODDIT_AUTHOR` une fois par session. `fm task whoami` indique sous quelle identité une
|
|
163
|
+
écriture signerait : le compte et l'espace connectés une fois que `fm login`/`--host` résout le
|
|
164
|
+
mode distant, sinon l'identité locale apposée sur chaque note. `fm task briefs` liste le travail
|
|
165
|
+
déposé par le responsable que personne n'a encore pris ; `fm task claim <ref>` en prend un.
|
|
166
|
+
Lancez `fm task --help` pour la liste complète des commandes et `fm task <commande> --help` pour
|
|
167
|
+
ses options.
|
|
168
|
+
|
|
169
|
+
#### Plugin Claude Code
|
|
170
|
+
|
|
171
|
+
Le dépôt git, pas le paquet `pipx`, est aussi un plugin Claude Code : `hooks/hooks.json` injecte
|
|
172
|
+
les règles d'usage de `fm task` et les nœuds encore ouverts du projet au début d'une session, et
|
|
173
|
+
`monitors/monitors.json` démarre `fm task monitor --here` pour que les réponses du responsable
|
|
174
|
+
atteignent l'agent sans qu'il ait à interroger en boucle. Il n'est pas publié sur un
|
|
175
|
+
marketplace, donc chargez-le depuis un clone plutôt que depuis le paquet installé :
|
|
176
|
+
|
|
177
|
+
```sh
|
|
178
|
+
git clone https://github.com/WeCarbon/formist-cli
|
|
179
|
+
claude --plugin-dir formist-cli
|
|
180
|
+
```
|
|
181
|
+
|
|
129
182
|
## FAQ
|
|
130
183
|
|
|
131
184
|
**Ai-je besoin des droits d'administration de la plateforme pour utiliser cet outil ?**
|
|
@@ -32,8 +32,8 @@ changes data always shows what it would do first; committing is a separate, expl
|
|
|
32
32
|
and where each came from, a flag, a remembered default, or nothing, so a wrong target is caught
|
|
33
33
|
by reading the screen, not by its effect.
|
|
34
34
|
- **Dry run by default.** A command that changes data prints what it would do and waits for
|
|
35
|
-
`--apply`. `fm
|
|
36
|
-
matches before committing, so a stale read can't turn into a wrong write.
|
|
35
|
+
`--apply`. `fm participants dedupe`, which merges a group of duplicate rows, re-checks the plan
|
|
36
|
+
still matches before committing, so a stale read can't turn into a wrong write.
|
|
37
37
|
- **A credential per deployment.** `fm login` stores an OAuth credential at `0600`, one file per
|
|
38
38
|
host, so signing in to a staging deployment never touches production. `FORMIST_TOKEN` supplies
|
|
39
39
|
one for CI: used as-is, never written to disk, never refreshed.
|
|
@@ -99,7 +99,7 @@ remembered host: name it with `--host`, or the default (`formist`) is used.
|
|
|
99
99
|
### Writes
|
|
100
100
|
|
|
101
101
|
Most commands that change data run as a dry run first and print what they would do; add
|
|
102
|
-
`--apply` to commit. `fm
|
|
102
|
+
`--apply` to commit. `fm participants dedupe`, which merges a group of duplicate rows, is slightly
|
|
103
103
|
different: the dry run prints a plan token, and `--apply <token>` re-runs the dry run to confirm
|
|
104
104
|
the plan still matches before committing. A handful of actions with no undo, such as `fm spaces
|
|
105
105
|
--admin delete`, have no dry run at all and say so in their own `--help`.
|
|
@@ -114,6 +114,56 @@ needs no login, `fm doctor` rolls health up across every deployment, and the res
|
|
|
114
114
|
`skill-library-install`, `meeting`, `project`, `connector`, `skills-add`, `skills-update`,
|
|
115
115
|
`proposals`, `audit-log`, `connectors`, `files`, read or write your own space the same way.
|
|
116
116
|
|
|
117
|
+
### Tasks (`fm task`)
|
|
118
|
+
|
|
119
|
+
`fm task` is a built-in port of [`nod`](https://github.com/wecarbon/noddit)'s task-and-decision
|
|
120
|
+
tracker: a node is one piece of work, a task when an AI can just do it, a decision when the
|
|
121
|
+
owner has to rule on it. It runs in one of two modes:
|
|
122
|
+
|
|
123
|
+
- **Logged out**, in any project: `fm task init` creates a `decisions/` folder, and every
|
|
124
|
+
command below finds it by walking up from the current directory, the same way `git` finds
|
|
125
|
+
`.git`. Nothing leaves the machine.
|
|
126
|
+
- **Logged in**, with `fm login`: `fm task --host <deployment>` (or a remembered `fm use` host
|
|
127
|
+
with a stored credential) talks to that space's node API instead, so a team shares one
|
|
128
|
+
tracker through Formist/Evane rather than a per-clone folder. Not every verb has a server
|
|
129
|
+
route yet; one that doesn't says so rather than guessing.
|
|
130
|
+
|
|
131
|
+
```sh
|
|
132
|
+
fm task init # creates decisions/ here
|
|
133
|
+
fm task add "Write the onboarding doc" --task # a new node
|
|
134
|
+
fm task start X1 # to do -> in progress
|
|
135
|
+
fm task note X1 "found last year's draft" # progress, without closing it
|
|
136
|
+
fm task show active # every open node (bare `show` lists only ones needing a decision)
|
|
137
|
+
fm task done X1 --note "doc is up" # -> done
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
A decision looks the same, just with options instead of `--task`:
|
|
141
|
+
|
|
142
|
+
```sh
|
|
143
|
+
fm task add "Which domain for staging" -o 1="api-staging.example.com" -o 2="staging-api.example.com"
|
|
144
|
+
fm task push X2 1 --note "matches the cert" # the owner's answer, recorded on the node
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
Every write needs an author: pass `--author "<you> · <doing what>"` or export `NODDIT_AUTHOR`
|
|
148
|
+
once per session. `fm task whoami` reports who a write would sign as: the signed-in account and
|
|
149
|
+
space once `fm login`/`--host` resolves to cloud mode, otherwise the local identity stamped on
|
|
150
|
+
each note. `fm task briefs` lists work the owner filed that nobody has picked up yet;
|
|
151
|
+
`fm task claim <ref>` takes one. Run `fm task --help` for the full verb list and `fm task <verb>
|
|
152
|
+
--help` for its flags.
|
|
153
|
+
|
|
154
|
+
#### Claude Code plugin
|
|
155
|
+
|
|
156
|
+
The git repo, not the `pipx` package, is also a Claude Code plugin: `hooks/hooks.json` injects
|
|
157
|
+
the `fm task` usage rules and the project's open nodes at the start of a session, and
|
|
158
|
+
`monitors/monitors.json` starts `fm task monitor --here` so the owner's replies reach the agent
|
|
159
|
+
without it polling. It isn't published to a marketplace, so load it from a clone instead of the
|
|
160
|
+
installed package:
|
|
161
|
+
|
|
162
|
+
```sh
|
|
163
|
+
git clone https://github.com/WeCarbon/formist-cli
|
|
164
|
+
claude --plugin-dir formist-cli
|
|
165
|
+
```
|
|
166
|
+
|
|
117
167
|
## FAQ
|
|
118
168
|
|
|
119
169
|
**Do I need platform-admin access to use this?**
|
|
@@ -30,9 +30,9 @@
|
|
|
30
30
|
- **先说清楚来源,再动手。** 每条命令都会报告它解析出的部署和空间,以及这些值是
|
|
31
31
|
从哪里来的:一个参数、一个记住的默认值,还是什么都没有。目标选错了,看屏幕就能
|
|
32
32
|
发现,不用等出了事才知道。
|
|
33
|
-
- **默认先试运行。** 会改数据的命令,先打印它会做什么,等着你传 `--apply
|
|
34
|
-
|
|
35
|
-
|
|
33
|
+
- **默认先试运行。** 会改数据的命令,先打印它会做什么,等着你传 `--apply`。合并
|
|
34
|
+
重复行的 `fm participants dedupe` 更进一步:提交前会重新核对这份计划是否还和刚
|
|
35
|
+
才的试运行一致,防止一次过时的读取变成一次错误的写入。
|
|
36
36
|
- **凭证按部署分开存。** `fm login` 把 OAuth 凭证存成 `0600` 权限的文件,每个部署
|
|
37
37
|
一个文件,登录测试环境绝不会动到生产环境。CI 场景用 `FORMIST_TOKEN` 提供凭证:
|
|
38
38
|
读到就用,不落盘,不自动刷新。
|
|
@@ -98,10 +98,10 @@ fm kb search "venue contract" --space <space-id>
|
|
|
98
98
|
### 写操作
|
|
99
99
|
|
|
100
100
|
大多数会改数据的命令都会先试运行,打印出它会做什么;加上 `--apply` 才会真正提交。
|
|
101
|
-
`fm
|
|
102
|
-
token),`--apply <令牌>`
|
|
103
|
-
|
|
104
|
-
|
|
101
|
+
`fm participants dedupe` 稍微不一样,它会合并一组重复记录:试运行会打印一个计划
|
|
102
|
+
令牌(plan token),`--apply <令牌>` 会重新跑一次试运行,确认这份计划还和当初一
|
|
103
|
+
致,然后才提交。少数不可撤销的操作,比如 `fm spaces --admin delete`,根本没有试
|
|
104
|
+
运行这一步,各自的 `--help` 里会写清楚。
|
|
105
105
|
|
|
106
106
|
### 命令
|
|
107
107
|
|
|
@@ -113,6 +113,51 @@ token),`--apply <令牌>` 会重新跑一次试运行,确认这份计划还和
|
|
|
113
113
|
`meeting`、`project`、`connector`、`skills-add`、`skills-update`、`proposals`、
|
|
114
114
|
`audit-log`、`connectors`、`files`,也都是以同样的方式读写你自己的空间。
|
|
115
115
|
|
|
116
|
+
### 任务(`fm task`)
|
|
117
|
+
|
|
118
|
+
`fm task` 内置了 [`nod`](https://github.com/wecarbon/noddit) 那套任务与决策跟踪器:一个节点就是
|
|
119
|
+
一件事,AI 能直接做的是任务,需要负责人先拍板的是决策。它有两种模式:
|
|
120
|
+
|
|
121
|
+
- **未登录**,在任意项目里:`fm task init` 会建一个 `decisions/` 文件夹,下面每条命令都从当前
|
|
122
|
+
目录往上找它,和 `git` 找 `.git` 的方式一样。什么都不会发出去。
|
|
123
|
+
- **已登录**,配合 `fm login`:`fm task --host <部署>`(或者 `fm use` 记住的、带凭证的 host)会
|
|
124
|
+
改成调用那个空间的节点接口,这样一个团队就能通过 Formist/Evane 共用一套跟踪器,而不是各自
|
|
125
|
+
一份本地文件夹。不是每个子命令在云端都已经接通,没接通的会直接说明,不会瞎猜。
|
|
126
|
+
|
|
127
|
+
```sh
|
|
128
|
+
fm task init # creates decisions/ here
|
|
129
|
+
fm task add "Write the onboarding doc" --task # a new node
|
|
130
|
+
fm task start X1 # to do -> in progress
|
|
131
|
+
fm task note X1 "found last year's draft" # progress, without closing it
|
|
132
|
+
fm task show active # every open node (bare `show` lists only ones needing a decision)
|
|
133
|
+
fm task done X1 --note "doc is up" # -> done
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
决策用的是同一套命令,只是把 `--task` 换成几个选项:
|
|
137
|
+
|
|
138
|
+
```sh
|
|
139
|
+
fm task add "Which domain for staging" -o 1="api-staging.example.com" -o 2="staging-api.example.com"
|
|
140
|
+
fm task push X2 1 --note "matches the cert" # the owner's answer, recorded on the node
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
每次写操作都要有作者:传 `--author "<你> · 在做什么"`,或者整个会话提前导出一次
|
|
144
|
+
`NODDIT_AUTHOR`。`fm task whoami` 会报出一次写操作会签成谁:云端模式下是登录账号和空间,
|
|
145
|
+
本地模式下就是写进每条笔记里的那个身份。`fm task briefs` 列出负责人派过、但还没人接手的活;
|
|
146
|
+
`fm task claim <节点>` 接下一个。完整子命令列表看 `fm task --help`,每个子命令的参数看
|
|
147
|
+
`fm task <子命令> --help`。
|
|
148
|
+
|
|
149
|
+
#### Claude Code 插件
|
|
150
|
+
|
|
151
|
+
这个 git 仓库本身(不是 `pipx` 装的那个包)同时也是一个 Claude Code 插件:`hooks/hooks.json`
|
|
152
|
+
会在每个会话开始时注入 `fm task` 的用法规则和项目里还没完成的节点,`monitors/monitors.json`
|
|
153
|
+
会起 `fm task monitor --here`,让负责人的答复能传到 AI 那里,不用它自己去轮询。这个插件还没
|
|
154
|
+
发布到插件市场,所以要从仓库的副本里加载,而不是已安装的包:
|
|
155
|
+
|
|
156
|
+
```sh
|
|
157
|
+
git clone https://github.com/WeCarbon/formist-cli
|
|
158
|
+
claude --plugin-dir formist-cli
|
|
159
|
+
```
|
|
160
|
+
|
|
116
161
|
## 常见问题
|
|
117
162
|
|
|
118
163
|
**用这个工具需要平台管理员权限吗?**
|