cowork-flow 0.0.2 → 0.0.4

package/template/.cowork-flow/scripts/task.py

@@ -4,18 +4,18 @@
 Task Management Script for cowork-flow workflow.
 
 Usage:
-    python3 task.py create "<title>" [--slug <name>] [--assignee <dev>] [--priority P0|P1|P2|P3] [--parent <dir>]
-    python3 task.py init-context <dir> <type>   # Initialize jsonl files
-    python3 task.py add-context <dir> <file> <path> [reason] # Add jsonl entry
-    python3 task.py validate <dir>              # Validate jsonl files
-    python3 task.py list-context <dir>          # List jsonl entries
-    python3 task.py start <dir>                 # Set as current task
-    python3 task.py finish                      # Clear current task
-    python3 task.py archive <task-name>         # Archive completed task
-    python3 task.py list                        # List active tasks
-    python3 task.py list-archive [month]        # List archived tasks
-    python3 task.py add-subtask <parent-dir> <child-dir>     # Link child to parent
-    python3 task.py remove-subtask <parent-dir> <child-dir>  # Unlink child from parent
+    ./.cowork-flow/run task create "<title>" [--slug <name>] [--assignee <dev>] [--priority P0|P1|P2|P3] [--parent <dir>]
+    ./.cowork-flow/run task init-context <dir> <type>   # Initialize jsonl files
+    ./.cowork-flow/run task add-context <dir> <file> <path> [reason] # Add jsonl entry
+    ./.cowork-flow/run task validate <dir>              # Validate jsonl files
+    ./.cowork-flow/run task list-context <dir>          # List jsonl entries
+    ./.cowork-flow/run task start <dir>                 # Set as current task
+    ./.cowork-flow/run task finish                      # Clear current task
+    ./.cowork-flow/run task archive <task-name>         # Archive completed task
+    ./.cowork-flow/run task list                        # List active tasks
+    ./.cowork-flow/run task list-archive [month]        # List archived tasks
+    ./.cowork-flow/run task add-subtask <parent-dir> <child-dir>     # Link child to parent
+    ./.cowork-flow/run task remove-subtask <parent-dir> <child-dir>  # Unlink child from parent
 """
 
 from __future__ import annotations
@@ -382,7 +382,10 @@ def _resolve_task_dir(target_dir: str, repo_root: Path) -> Path:
 def get_implement_base() -> list[dict]:
     """Get base implement context entries."""
     return [
+        {"file": "AGENTS.md", "reason": "Project collaboration rules and workflow gates"},
         {"file": f"{DIR_WORKFLOW}/workflow.md", "reason": "Project workflow and conventions"},
+        {"file": f"{DIR_WORKFLOW}/{DIR_SPEC}/guides/index.md", "reason": "Pre-implementation thinking guides"},
+        {"file": f"{DIR_WORKFLOW}/{DIR_SPEC}/guides/pre-implementation-checklist.md", "reason": "Mandatory pre-coding checklist"},
     ]
 
 
@@ -408,6 +411,7 @@ def get_check_context(dev_type: str, repo_root: Path) -> list[dict]:
     """Get check context entries."""
     entries = [
         {"file": _skill_path("finish-work"), "reason": "Finish work checklist"},
+        {"file": _skill_path("record-session"), "reason": "Session recording and state sync"},
     ]
 
     if dev_type in ("backend", "frontend", "fullstack"):
@@ -420,6 +424,7 @@ def get_debug_context(dev_type: str, repo_root: Path) -> list[dict]:
     """Get debug context entries."""
     entries: list[dict] = [
         {"file": _skill_path("break-loop"), "reason": "Deep bug analysis workflow"},
+        {"file": _skill_path("update-spec"), "reason": "Capture implementation lessons and contracts"},
     ]
 
     if dev_type in ("backend", "frontend", "fullstack"):
@@ -434,6 +439,53 @@ def _write_jsonl(path: Path, entries: list[dict]) -> None:
     path.write_text("\n".join(lines) + "\n", encoding="utf-8")
 
 
+def _read_text_if_present(path: Path) -> str:
+    """读取文本文件并返回去空白后的内容；不存在或读取失败时返回空字符串。"""
+    if not path.is_file():
+        return ""
+
+    try:
+        return path.read_text(encoding="utf-8").strip()
+    except (OSError, IOError):
+        return ""
+
+
+def _task_start_blockers(task_dir: Path) -> list[str]:
+    """返回启动任务前必须处理的准备阻塞项。"""
+    blockers: list[str] = []
+
+    task_json = task_dir / FILE_TASK_JSON
+    if not task_json.is_file():
+        blockers.append("task.json is missing")
+
+    prd_file = task_dir / "prd.md"
+    if not _read_text_if_present(prd_file):
+        blockers.append("prd.md is missing or empty")
+
+    for jsonl_name in CONTEXT_JSONL_FILES:
+        jsonl_file = task_dir / jsonl_name
+        if not _read_text_if_present(jsonl_file):
+            blockers.append(f"{jsonl_name} is missing or empty")
+
+    return blockers
+
+
+def _task_context_validation_issues(task_dir: Path, repo_root: Path) -> list[str]:
+    """返回任务上下文文件的校验问题。"""
+    issues: list[str] = []
+
+    for jsonl_name in CONTEXT_JSONL_FILES:
+        jsonl_file = task_dir / jsonl_name
+        if not _read_text_if_present(jsonl_file):
+            continue
+
+        error_count = _validate_jsonl(jsonl_file, repo_root)
+        if error_count > 0:
+            issues.append(f"{jsonl_name} has {error_count} validation error(s)")
+
+    return issues
+
+
 def _iter_jsonl_lines(path: Path):
     """Yield line number and content from a JSONL file."""
     with path.open("r", encoding="utf-8") as f:
@@ -578,8 +630,8 @@ def cmd_create(args: argparse.Namespace) -> int:
     print("", file=sys.stderr)
     print(colored("Next steps:", Colors.BLUE), file=sys.stderr)
     print("  1. Create prd.md with requirements", file=sys.stderr)
-    print("  2. Run: python3 task.py init-context <dir> <dev_type>", file=sys.stderr)
-    print("  3. Run: python3 task.py start <dir>", file=sys.stderr)
+    print("  2. Run: ./.cowork-flow/run task init-context <dir> <dev_type>", file=sys.stderr)
+    print("  3. Run: ./.cowork-flow/run task start <dir>", file=sys.stderr)
     print("", file=sys.stderr)
 
     # Output relative path for script chaining
@@ -601,7 +653,7 @@ def cmd_init_context(args: argparse.Namespace) -> int:
 
     if not dev_type:
         print(colored("Error: Missing arguments", Colors.RED))
-        print("Usage: python3 task.py init-context <task-dir> <dev_type>")
+        print("Usage: ./.cowork-flow/run task init-context <task-dir> <dev_type>")
         print("  dev_type: backend | frontend | fullstack | test | docs")
         return 1
 
@@ -647,8 +699,8 @@ def cmd_init_context(args: argparse.Namespace) -> int:
     print(colored("[OK] All context files created", Colors.GREEN))
     print()
     print(colored("Next steps:", Colors.BLUE))
-    print("  1. Add task-specific specs: python3 task.py add-context <dir> <jsonl> <path>")
-    print("  2. Set as current: python3 task.py start <dir>")
+    print("  1. Add task-specific specs: ./.cowork-flow/run task add-context <dir> <jsonl> <path>")
+    print("  2. Set as current: ./.cowork-flow/run task start <dir>")
 
     return 0
 
@@ -856,6 +908,28 @@ def cmd_start(args: argparse.Namespace) -> int:
         print(f"Hint: Use task name (e.g., 'my-task') or full path (e.g., '{DIR_WORKFLOW}/tasks/01-31-my-task')")
         return 1
 
+    blockers = _task_start_blockers(full_path)
+    if blockers:
+        print(colored("Error: Task is not ready to start yet", Colors.RED), file=sys.stderr)
+        for blocker in blockers:
+            print(f"  - {blocker}", file=sys.stderr)
+        print(
+            "Hint: write prd.md, run ./.cowork-flow/run task init-context <dir> <dev_type>, then retry",
+            file=sys.stderr,
+        )
+        return 1
+
+    validation_issues = _task_context_validation_issues(full_path, repo_root)
+    if validation_issues:
+        print(colored("Error: Task context validation failed", Colors.RED), file=sys.stderr)
+        for issue in validation_issues:
+            print(f"  - {issue}", file=sys.stderr)
+        print(
+            "Hint: run ./.cowork-flow/run task validate <dir> and fix the reported issues",
+            file=sys.stderr,
+        )
+        return 1
+
     # Convert to relative path for storage
     try:
         task_dir = str(full_path.relative_to(repo_root))
@@ -1237,19 +1311,19 @@ def show_usage() -> None:
     print("""Task Management Script for cowork-flow workflow
 
 Usage:
-  python3 task.py create <title>                     Create new task directory
-  python3 task.py create <title> --parent <dir>      Create task as child of parent
-  python3 task.py init-context <dir> <dev_type>      Initialize jsonl files
-  python3 task.py add-context <dir> <jsonl> <path> [reason]  Add entry to jsonl
-  python3 task.py validate <dir>                     Validate jsonl files
-  python3 task.py list-context <dir>                 List jsonl entries
-  python3 task.py start <dir>                        Set as current task
-  python3 task.py finish                             Clear current task
-  python3 task.py archive <task-name>                Archive completed task
-  python3 task.py add-subtask <parent> <child>       Link child task to parent
-  python3 task.py remove-subtask <parent> <child>    Unlink child from parent
-  python3 task.py list [--mine] [--status <status>]  List tasks
-  python3 task.py list-archive [YYYY-MM]             List archived tasks
+  ./.cowork-flow/run task create <title>                     Create new task directory
+  ./.cowork-flow/run task create <title> --parent <dir>      Create task as child of parent
+  ./.cowork-flow/run task init-context <dir> <dev_type>      Initialize jsonl files
+  ./.cowork-flow/run task add-context <dir> <jsonl> <path> [reason]  Add entry to jsonl
+  ./.cowork-flow/run task validate <dir>                     Validate jsonl files
+  ./.cowork-flow/run task list-context <dir>                 List jsonl entries
+  ./.cowork-flow/run task start <dir>                        Set as current task
+  ./.cowork-flow/run task finish                             Clear current task
+  ./.cowork-flow/run task archive <task-name>                Archive completed task
+  ./.cowork-flow/run task add-subtask <parent> <child>       Link child task to parent
+  ./.cowork-flow/run task remove-subtask <parent> <child>    Unlink child from parent
+  ./.cowork-flow/run task list [--mine] [--status <status>]  List tasks
+  ./.cowork-flow/run task list-archive [YYYY-MM]             List archived tasks
 
 Arguments:
   dev_type: backend | frontend | fullstack | test | docs
@@ -1259,18 +1333,18 @@ List options:
   --status, -s <s>     Filter by status (planning, in_progress, review, completed)
 
 Examples:
-  python3 task.py create "Add login feature" --slug add-login
-  python3 task.py create "Child task" --slug child --parent .cowork-flow/tasks/01-21-parent
-  python3 task.py init-context .cowork-flow/tasks/01-21-add-login backend
-  python3 task.py add-context <dir> implement .cowork-flow/spec/backend/auth.md "Auth guidelines"
-  python3 task.py start .cowork-flow/tasks/01-21-add-login
-  python3 task.py finish
-  python3 task.py archive add-login
-  python3 task.py add-subtask parent-task child-task  # Link existing tasks
-  python3 task.py remove-subtask parent-task child-task
-  python3 task.py list                               # List all active tasks
-  python3 task.py list --mine                        # List my tasks only
-  python3 task.py list --mine --status in_progress   # List my in-progress tasks
+  ./.cowork-flow/run task create "Add login feature" --slug add-login
+  ./.cowork-flow/run task create "Child task" --slug child --parent .cowork-flow/tasks/01-21-parent
+  ./.cowork-flow/run task init-context .cowork-flow/tasks/01-21-add-login backend
+  ./.cowork-flow/run task add-context <dir> implement .cowork-flow/spec/backend/auth.md "Auth guidelines"
+  ./.cowork-flow/run task start .cowork-flow/tasks/01-21-add-login
+  ./.cowork-flow/run task finish
+  ./.cowork-flow/run task archive add-login
+  ./.cowork-flow/run task add-subtask parent-task child-task  # Link existing tasks
+  ./.cowork-flow/run task remove-subtask parent-task child-task
+  ./.cowork-flow/run task list                               # List all active tasks
+  ./.cowork-flow/run task list --mine                        # List my tasks only
+  ./.cowork-flow/run task list --mine --status in_progress   # List my in-progress tasks
 """)
 
 

package/template/.cowork-flow/spec/guides/pre-implementation-checklist.md

@@ -4,7 +4,7 @@
 
 - 这次改动属于 `L0`、`L1` 还是 `L2`？
 - 是否涉及 API、数据库、异步链路、权限或状态流转？
-- 是否需要先补 OpenSpec？
+- 是否需要先补 `cowork-flow change`？
 - 是否已经明确成功标准和验证方式？
 - 是否已经搜索过相似实现与可复用能力？
 

package/template/.cowork-flow/workflow.md

@@ -10,6 +10,8 @@
 
 所有任务都应先明确目标和验收标准，再进入实现；所有完成结论都必须有验证证据支撑。
 
+命令示例默认使用 macOS / Linux / Git Bash / WSL 写法；Windows cmd / PowerShell 中使用 `.\.cowork-flow\run.cmd <command>` 替代 `./.cowork-flow/run <command>`。
+
 ---
 
 ## 2. 职责边界
@@ -70,8 +72,8 @@
 首次进入项目时执行：
 
 ```bash
-python3 ./.cowork-flow/scripts/get_developer.py
-python3 ./.cowork-flow/scripts/init_developer.py <developer-name>
+./.cowork-flow/run get-developer
+./.cowork-flow/run init-developer <developer-name>
 ```
 
 如果已经存在开发者身份，只需读取当前身份。
@@ -81,8 +83,8 @@ python3 ./.cowork-flow/scripts/init_developer.py <developer-name>
 每次开始工作先执行：
 
 ```bash
-python3 ./.cowork-flow/scripts/get_context.py
-python3 ./.cowork-flow/scripts/task.py list
+./.cowork-flow/run resume
+./.cowork-flow/run task list
 git status
 git log --oneline -10
 ```
@@ -167,8 +169,8 @@ cowork-flow change -> brainstorming -> design.md -> writing-plans -> 任务上
 ### 6.1 创建或选择任务
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py list
-python3 ./.cowork-flow/scripts/task.py create "<title>" --slug <task-name>
+./.cowork-flow/run task list
+./.cowork-flow/run task create "<title>" --slug <task-name>
 ```
 
 ### 6.2 写入任务 PRD
@@ -184,7 +186,7 @@ python3 ./.cowork-flow/scripts/task.py create "<title>" --slug <task-name>
 ### 6.3 初始化任务上下文
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py init-context <task-dir> <type>
+./.cowork-flow/run task init-context <task-dir> <type>
 ```
 
 `<type>` 按任务选择：
@@ -200,14 +202,14 @@ python3 ./.cowork-flow/scripts/task.py init-context <task-dir> <type>
 把任务相关规范、代码模式、计划文件加入上下文：
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py add-context <task-dir> implement <path> "<reason>"
-python3 ./.cowork-flow/scripts/task.py add-context <task-dir> check <path> "<reason>"
+./.cowork-flow/run task add-context <task-dir> implement <path> "<reason>"
+./.cowork-flow/run task add-context <task-dir> check <path> "<reason>"
 ```
 
 ### 6.5 激活任务并执行
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py start <task-dir>
+./.cowork-flow/run task start <task-dir>
 ```
 
 执行要求：
@@ -225,7 +227,7 @@ python3 ./.cowork-flow/scripts/task.py start <task-dir>
 ### 7.1 创建 cowork-flow change
 
 ```bash
-python3 ./.cowork-flow/scripts/change.py create <slug>
+./.cowork-flow/run change create <slug>
 ```
 
 ### 7.2 使用 brainstorming 形成方案
@@ -233,13 +235,13 @@ python3 ./.cowork-flow/scripts/change.py create <slug>
 使用 `superpowers:brainstorming` 澄清需求、比较方案，并补齐：
 
 - `.cowork-flow/changes/<slug>/proposal.md`
-- `.cowork-flow/changes/<slug>/specs/.../spec.md`
+- `.cowork-flow/changes/<slug>/spec.md`
 - L2 任务需要 `.cowork-flow/changes/<slug>/design.md`
 
 ### 7.3 校验 cowork-flow change
 
 ```bash
-python3 ./.cowork-flow/scripts/change.py validate <slug>
+./.cowork-flow/run change validate <slug>
 ```
 
 ### 7.4 使用 writing-plans 形成计划
@@ -345,8 +347,8 @@ L2 任务完成前需要多视角审阅：
 ### 9.2 记录 session
 
 ```bash
-python3 ./.cowork-flow/scripts/get_context.py --mode record
-python3 ./.cowork-flow/scripts/add_session.py \
+./.cowork-flow/run get-context --mode record
+./.cowork-flow/run add-session \
   --title "<session-title>" \
   --commit "<commit-or-handoff-ref>" \
   --summary "<summary>"
@@ -357,13 +359,13 @@ python3 ./.cowork-flow/scripts/add_session.py \
 仅在任务真实完成后归档：
 
 ```bash
-python3 ./.cowork-flow/scripts/task.py archive <task-name>
+./.cowork-flow/run task archive <task-name>
 ```
 
 行为变更任务还需要归档 cowork-flow change：
 
 ```bash
-python3 ./.cowork-flow/scripts/change.py archive <slug>
+./.cowork-flow/run change archive <slug>
 ```
 
 ---
@@ -387,7 +389,29 @@ python3 ./.cowork-flow/scripts/change.py archive <slug>
 
 ---
 
-## 11. 禁止事项
+## 11. 恢复与上下文压缩
+
+多轮对话、长任务、中断恢复或上下文压缩后，必须先走最小恢复层，再按需读取细节。
+
+| 层级 | 读取内容 | 使用时机 |
+|------|----------|----------|
+| 最小恢复层 | `resume.py` 输出中的 `RESUME CHECKLIST` | 每次恢复、压缩后、重新接手任务 |
+| 任务执行层 | 当前任务 `prd.md`、当前 plan 状态、`task.py list-context <task-dir>` | 准备继续实现或检查前 |
+| 细节规范层 | jsonl 指向的具体 spec、代码模式或计划段落 | 当前修改确实需要该细节时 |
+
+恢复规则：
+
+- 先执行 `./.cowork-flow/run resume`。
+- 按 `RESUME CHECKLIST` 读取当前 PRD、当前 plan 和 `list-context` 输出。
+- 不要全量重读 `.cowork-flow/spec/`、所有 plan、所有 task 或 workspace journal。
+- 如果 plan 有 `Current Execution Status`，先读该段以确定下一步。
+- 如果 jsonl 指向的规范过多，先根据当前阶段选择最小相关集合。
+
+恢复目标是重建“现在该做什么”和“当前门禁是否满足”，不是把全部历史重新塞进上下文。
+
+---
+
+## 12. 禁止事项
 
 - 不跳过上下文读取直接编码。
 - 不在未验证时声称完成。
@@ -398,7 +422,7 @@ python3 ./.cowork-flow/scripts/change.py archive <slug>
 
 ---
 
-## 12. 完成定义
+## 13. 完成定义
 
 一个任务只有在以下条件同时满足时，才算完成：
 

package/template/.cowork-flow/workspace/index.md

@@ -33,14 +33,14 @@ workspace/
 ### 新开发者
 
 ```bash
-python3 ./.cowork-flow/scripts/init_developer.py <your-name>
+./.cowork-flow/run init-developer <your-name>
 ```
 
 ### 已初始化开发者
 
 ```bash
-python3 ./.cowork-flow/scripts/get_developer.py
-cat .cowork-flow/workspace/$(python3 ./.cowork-flow/scripts/get_developer.py)/index.md
+./.cowork-flow/run get-developer
+cat .cowork-flow/workspace/$(./.cowork-flow/run get-developer)/index.md
 ```
 
 ---

package/template/.superpowers/brainstorming/SKILL.md

@@ -26,7 +26,7 @@ You MUST create a task for each of these items and complete them in order:
 3. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
 4. **Propose 2-3 approaches** — with trade-offs and your recommendation
 5. **Present design** — in sections scaled to their complexity, get user approval after each section
-6. **Write design doc** — save to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit
+6. **Write change artifacts** — save proposal/spec/design in `.cowork-flow/changes/<slug>/` and commit
 7. **Spec self-review** — quick inline check for placeholders, contradictions, ambiguity, scope (see below)
 8. **User reviews written spec** — ask user to review the spec file before proceeding
 9. **Transition to implementation** — invoke writing-plans skill to create implementation plan
@@ -108,7 +108,10 @@ digraph brainstorming {
 
 **Documentation:**
 
-- Write the validated design (spec) to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
+- Write the validated change artifacts under `.cowork-flow/changes/<slug>/`
+  - `proposal.md` explains why the behavior should change
+  - `spec.md` defines external behavior and acceptance criteria
+  - `design.md` records important design trade-offs for L2 work
   - (User preferences for spec location override this default)
 - Use elements-of-style:writing-clearly-and-concisely skill if available
 - Commit the design document to git

package/template/.superpowers/brainstorming/spec-document-reviewer-prompt.md

@@ -4,7 +4,7 @@ Use this template when dispatching a spec document reviewer subagent.
 
 **Purpose:** Verify the spec is complete, consistent, and ready for implementation planning.
 
-**Dispatch after:** Spec document is written to docs/superpowers/specs/
+**Dispatch after:** Spec or design document is written under `.cowork-flow/changes/<slug>/`
 
 ```
 Task tool (general-purpose):

package/template/.superpowers/requesting-code-review/SKILL.md

@@ -57,7 +57,7 @@ HEAD_SHA=$(git rev-parse HEAD)
 
 [Dispatch code reviewer subagent]
   DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
-  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
+  PLAN_OR_REQUIREMENTS: Task 2 from .cowork-flow/plans/deployment-plan.md
   BASE_SHA: a7981ec
   HEAD_SHA: 3df7661
 

package/template/.superpowers/subagent-driven-development/SKILL.md

@@ -130,7 +130,7 @@ Implementer subagents report one of four statuses. Handle each appropriately:
 ```
 You: I'm using Subagent-Driven Development to execute this plan.
 
-[Read plan file once: docs/superpowers/plans/feature-plan.md]
+[Read plan file once: .cowork-flow/plans/feature-plan.md]
 [Extract all 5 tasks with full text and context]
 [Create TodoWrite with all tasks]
 

package/template/.superpowers/writing-plans/SKILL.md

@@ -15,7 +15,7 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
 
 **Context:** If working in an isolated worktree, it should have been created via the `superpowers:using-git-worktrees` skill at execution time.
 
-**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
+**Save plans to:** `.cowork-flow/plans/YYYY-MM-DD-<feature-name>.md`
 - (User preferences for plan location override this default)
 
 ## Scope Check
@@ -135,7 +135,7 @@ If you find issues, fix them inline. No need to re-review — just fix and move
 
 After saving the plan, offer execution choice:
 
-**"Plan complete and saved to `docs/superpowers/plans/<filename>.md`. Two execution options:**
+**"Plan complete and saved to `.cowork-flow/plans/<filename>.md`. Two execution options:**
 
 **1. Subagent-Driven (recommended)** - I dispatch a fresh subagent per task, review between tasks, fast iteration
 

package/template/AGENTS.md

@@ -95,14 +95,24 @@
     - 如果跟丢上下文，先停下来重新整理。
 
 <!-- COWORK-FLOW:START -->
-# cowork-flow Instructions
+# cowork-flow 强门禁
 
-These instructions are for AI assistants working in this project.
+若与项目自定义说明冲突，以项目说明和用户明确指令为准。
+
+命令示例默认使用 macOS / Linux / Git Bash / WSL 写法；Windows cmd / PowerShell 中使用 `.\.cowork-flow\run.cmd <command>` 替代 `./.cowork-flow/run <command>`。
+
+1. 每次新会话、重新接手任务、或上下文明显丢失时，先执行 `./.cowork-flow/run resume`，再进入 `.agent/skills/start`。
+2. 执行 `start` 时，先读 `AGENTS.md`、`.cowork-flow/workflow.md` 和 `resume.py` 的输出，不要直接编码。
+3. 任何会修改仓库文件的请求，都必须先分级为 `L0` / `L1` / `L2`，再进入对应流程；不要把“很小”当成可以绕过流程的理由。
+4. `L1` / `L2` 行为变更必须先有 `change -> spec -> plan`；`L2` 还必须有 `design.md`，然后才能进入实现。
+5. 实现前必须把任务上下文写入 `.cowork-flow/tasks/<task>/implement.jsonl`、`check.jsonl`、`debug.jsonl`，并在 `start` 之后再改代码。
+6. 收尾前必须跑验证、同步 plan / task / change 状态，完成 `finish-work` 检查，再按项目策略记录 session。
+7. 多轮对话、长任务恢复或上下文压缩后，先运行 `./.cowork-flow/run resume` 并查看 `RESUME CHECKLIST`；只读取清单列出的 PRD、当前 plan 和 jsonl 引用，不要全量重读 `.cowork-flow/spec/` 或历史 journal。
 
 Use the `.agent/skills/start` skill when starting a new session to:
 - Initialize your developer identity
 - Understand current project context
-- Read relevant guidelines
+- Enforce the task workflow gates before any implementation
 
 Use `@/.cowork-flow/` to learn:
 - Development workflow (`workflow.md`)