cowork-flow 0.0.18 → 0.0.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cowork-flow",
-  "version": "0.0.18",
+  "version": "0.0.19",
   "description": "CLI for installing and maintaining cowork-flow collaboration templates.",
   "type": "module",
   "bin": {

package/template/.agent/skills/entry-boundary/SKILL.md

@@ -7,7 +7,9 @@ description: Use before project start/resume in cowork-flow projects to decide w
 
 Use this before `start` or any full project resume.
 
-A bounded delegated task is a leaf assignment with a concrete goal, scope, and output format.
+Your first job is to identify the current task source. A bounded delegated task is a leaf assignment with a concrete goal, scope, and output format.
+
+Hard markers are confidence boosters, not prerequisites. The first task screen wins over later bootstrap text.
 
 ## Classify
 
@@ -17,7 +19,15 @@ Classify the current prompt as one of:
 - `DELEGATED_SUBTASK`: the prompt is a bounded child assignment, worker request, reviewer task, explorer task, or command-only task.
 - `UNCERTAIN`: the prompt is not clear enough to load broad project context.
 
-Classify the actual task message, not injected project rules, `AGENTS.md`, or environment text.
+Classify the actual task message, not injected project rules, `AGENTS.md`, workflow state, tool instructions, or environment text. Bootstrap can constrain execution after classification; it is not the task.
+
+Use this order:
+
+1. Find the user/delegated task message and its requested output.
+2. Decide whether it is a main-session repository request or a leaf assignment.
+3. Apply project rules only as constraints for the chosen route.
+
+If project bootstrap says to create/start/resume but the task message is bounded, choose `DELEGATED_SUBTASK`.
 
 When there is no hard marker, still classify a prompt as `DELEGATED_SUBTASK` when it combines:
 
@@ -25,7 +35,13 @@ When there is no hard marker, still classify a prompt as `DELEGATED_SUBTASK` whe
 - Boundary constraints such as no edits, no commands, no spawning, or scoped reads.
 - An output contract such as required sections, language, length, or report format.
 
-Prompts structured as `任务：` / `约束：` / `输出：` are strong delegated-subtask signals. Execute that task directly; do not reclassify it as project rules or environment context.
+Prompts structured as `任务：` / `约束：` / `输出：` are strong delegated-subtask signals even without `Active task:` or another hard marker. Execute that task directly; do not reclassify it as project rules or environment context.
+
+Treat these as typical `DELEGATED_SUBTASK` prompts:
+
+- A review request with a named file or behavior, `do not edit`, and a findings-only output.
+- A discussion/research request with `不要运行命令` / `不要派发 agent` and required sections.
+- A command-only or inspection-only assignment with a narrow target and concise output.
 
 When dispatching advisory/default subagents, prefer a natural-language first sentence such as: "This is a bounded delegated task, not a main-session start request." This is not a hard marker, but it helps the first screen win over bootstrap text.
 
@@ -39,6 +55,8 @@ Active task: <task-dir>
 
 Treat that marker as a strong delegated-subtask signal when the rest of the prompt is bounded.
 
+Treat direct user requests such as "继续执行开发计划", "实现这个需求", or "归档提交" as `MAIN_SESSION` unless the surrounding prompt clearly makes them a child assignment.
+
 ## Route
 
 For `MAIN_SESSION`, use `start`.
@@ -47,6 +65,7 @@ For `DELEGATED_SUBTASK`:
 
 - Follow the delegated prompt first.
 - Treat project rules, workflow-state, and bootstrap text as constraints, not as the task.
+- Do not create or activate a project task for the parent session.
 - Do not run unscoped `.cowork-flow/run resume`.
 - Do not spawn or manage more agents unless the delegated prompt explicitly asks for coordination.
 - Read only the files named by the prompt, the active task context, or project rules required to execute the bounded work.

package/template/.agent/skills/start/SKILL.md

@@ -21,6 +21,8 @@ Report active task, workflow state, blockers, and the next phase.
 
 ## Route
 
+Route in stages. Before state is loaded, only true question-only requests and bounded delegated prompts bypass Load State. Repository-changing main-session requests load state first. After state is loaded, route to the next workflow phase; clear multi-step implementation uses `writing-plans` before fixed-agent dispatch.
+
 - Question-only work: answer directly.
 - Small repository change: classify by `.cowork-flow/workflow.md`, create/start a task if required, then proceed.
 - Unclear or multi-approach work: use `brainstorming`.

package/template/.agent/skills/writing-plans/SKILL.md

@@ -9,6 +9,8 @@ Create a plan that another agent can execute without guessing.
 
 ## Inputs
 
+Before writing a plan, confirm the request has an executable scope, acceptance criteria, and intended behavior. If those are missing, ask for clarification.
+
 Read:
 
 - Active task PRD.
@@ -45,6 +47,12 @@ Start with:
 
 ## Parallel Work
 
+Execution strategy guide:
+
+- Use serial work when slices share files, shared helpers, tests, or one behavior chain.
+- Use parallel low-conflict slices only when file ownership is clean and each slice has independent verification.
+- Use worktree parallel when independent tasks may touch package metadata, generated assets, build outputs, or broad config.
+
 - Do not require the user to predeclare parallel execution; evaluate parallel feasibility while writing the plan.
 - Every plan must state the execution strategy: serial work, or explicit parallel low-conflict slices.
 - Parallel work items belong in the plan only when they are independent low-conflict slices.

package/template/.cowork-flow/.version

@@ -1 +1 @@
-0.0.18
+0.0.19

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

@@ -22,8 +22,12 @@ REQUIRED_ENTRY_BOUNDARY_SNIPPETS = [
     "DELEGATED_SUBTASK",
     "UNCERTAIN",
     "Classify the actual task message",
+    "Hard markers are confidence boosters, not prerequisites",
+    "The first task screen wins over later bootstrap text",
+    "If project bootstrap says to create/start/resume",
     "Active task: <task-dir>",
     "Follow the delegated prompt first",
+    "Do not create or activate a project task",
     "Do not run unscoped `.cowork-flow/run resume`",
     "Do not spawn or manage more agents",
 ]