clarify Scientify user flows and skill entry points

README.en.md

@@ -267,6 +267,10 @@ Check status anytime:
 | **research-review** | `/research-review` | Review implementation. Iterates fix → rerun → review up to 3 times. |
 | **research-experiment** | `/research-experiment` | Full training + ablation experiments. Requires review PASS. |
 | **idea-generation** | `/idea-generation` | Generate 5 innovative research ideas from a topic, select and enhance the best one. |
+| **write-paper** | `/write-paper` | Draft a result-driven paper or technical report from experiment artifacts. |
+| **artifact-review** | `/artifact-review` | Review a draft, README, or figure set before external sharing. |
+| **figure-standardize** | `/figure-standardize` | Normalize figure filenames, captions, labels, and reuse metadata. |
+| **release-layout** | `/release-layout` | Repackage existing artifacts into a clearer README or release entry surface. |
 
 </details>
 
@@ -306,7 +310,6 @@ Check status anytime:
 | `/papers` | List downloaded papers with metadata |
 | `/ideas` | List generated ideas |
 | `/projects` | List all projects |
-| `/project-switch <id>` | Switch active project |
 | `/project-delete <id>` | Delete a project |
 | `/research-subscribe ...` | Create/update scheduled Scientify jobs |
 | `/research-subscriptions` | Show your scheduled Scientify jobs |

README.md

@@ -250,6 +250,19 @@ openclaw gateway
 /ideas                 # 列出已生成想法
 ```
 
+## 中后段项目的快捷技能
+
+如果项目已经有一部分产物，不必总是从 `/metabolism` 或 `/research-survey` 重新开始。可以直接进入这些 skill：
+
+- `/write-paper`
+  - 适合：已经有 `experiment_res.md`、结果图或结果表，准备整理成 paper draft
+- `/artifact-review`
+  - 适合：已有 draft、README 更新或准备对外分享的 figures，想先做发布前审查
+- `/figure-standardize`
+  - 适合：图已经有了，但文件名、caption、单位、标签风格不统一
+- `/release-layout`
+  - 适合：项目已有成果，想把 README 或 release 入口改得更清楚、更适合外部阅读
+
 ---
 
 ## 已知限制

index.ts

@@ -18,7 +18,7 @@ import { handleMetabolismStatus } from "./src/commands/metabolism-status.js";
 export default definePluginEntry({
   id: "scientify",
   name: "Scientify",
-  description: "AI-powered research workflow automation with continuous knowledge metabolism",
+  description: "Continuous AI research workflow for survey, planning, implementation, review, experimentation, and writing",
   register(api) {
     // Register tools
     api.registerTool(createArxivSearchTool());

openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "scientify",
   "name": "Scientify",
-  "description": "AI-powered research workflow automation for OpenClaw",
+  "description": "Continuous AI research workflow for survey, planning, implementation, review, experimentation, and writing",
   "configSchema": {
     "type": "object",
     "additionalProperties": false,

src/templates/bootstrap.ts

@@ -19,6 +19,7 @@ You were just created as the research agent for project "${projectName}". Comple
 4. Once confirmed, write the following files:
    - update \`SOUL.md\` with the project direction and domain fields
    - generate \`config.json\` using the template below
+   - create \`progress_status.json\` for the current goal, including overall goal, current focus, next step, total tasks, completed tasks, and 3-7 subtasks
 5. Ask whether the user wants to run Day 0 immediately to build the initial knowledge state.
    - If yes, run \`/metabolism\` to perform the first literature retrieval and knowledge-base construction pass.
 6. If the project already has partial outputs, use the shortest matching path instead of restarting the full pipeline:
@@ -74,6 +75,7 @@ $W/
 ├── SOUL.md                      # identity and project direction
 ├── AGENTS.md                    # this document
 ├── config.json                  # project config (keywords, categories, current day)
+├── progress_status.json         # agent-defined task progress for the current goal
 │
 ├── papers/                      # literature artifacts
 │   ├── {arxiv_id}/              # arXiv source files
@@ -125,6 +127,12 @@ Check whether the output file already exists before running a step. If it exists
 ### Immutability
 Do not modify output files once written unless the user explicitly asks you to. Exception: \`project/\` may change during implement-review iteration.
 
+### Progress Tracking
+- Do not assume every project follows the same fixed stages.
+- Define progress in \`progress_status.json\` based on the user's current goal.
+- Update \`progress_status.json\` whenever the total task, current focus, subtask states, or next step changes.
+- Recommended fields: \`overall_goal\`, \`current_focus\`, \`next_step\`, \`completed_tasks\`, \`total_tasks\`, \`subtasks\`.
+
 ### Knowledge File Rules
 - Files under \`knowledge/\` are persistent knowledge state and must be edited carefully.
 - Always read the current file before updating it.