@guanlin4924/devflow-pi 0.1.93 → 0.1.95

package/plugins/devflow-core/skills/workflow-orchestrator/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: workflow-orchestrator
-description: Use when the user asks to continue, resume, advance, inspect, or route a .planning-based workflow; when the OMP development agent must decide the next workflow skill from project state; or when a checkpoint must be handled before proceeding.
+description: Use when the user asks to continue, resume, advance, inspect, or route a .devflow/planning-based workflow; when the OMP development agent must decide the next workflow skill from project state; or when a checkpoint must be handled before proceeding.
 ---
 
 # Workflow Orchestrator
 
 ## Overview
 
-Control-plane entrypoint for project workflows. Reads `.planning/STATE.md`, `.planning/workflows/*.yaml`, and the artifact registry, decides the next action, and preserves checkpoint gates. Pipeline delegates here after parameter parsing and breakpoint detection.
+Control-plane entrypoint for project workflows. Reads `.devflow/planning/STATE.md`, `.devflow/planning/workflows/*.yaml`, and the artifact registry, decides the next action, and preserves checkpoint gates. Pipeline delegates here after parameter parsing and breakpoint detection.
 
 This skill is the **single source of truth for all execution-time rules**: gate rules, CP protocol, failure branches, parallel windows, state writeback, lessons injection, and requirement writeback. Pipeline only handles entry (args + breakpoint).
 
@@ -51,7 +51,7 @@ When `blocked` includes a `recovery` command, run or propose that command before
 
 `inspect_state.rb` runs `validate_state.rb` before dispatching normal actions. If validation fails, stop at `action: blocked` and fix the reported state/artifact inconsistency before continuing. Do not treat `status: completed` as authoritative unless `validate_state.rb --json` returns `ok: true`.
 
-When `run_project_context` is returned, do not initialize workflow state manually first. Execute `workflow-project-context` with the user's provided codebase locations and project-init arguments, verify it writes `.planning/PROJECT.md`, `.planning/navigation/INDEX.md`, `.context/spec/index.md`, and `.planning/STATE.md`, then run `inspect_state.rb --json` again and continue from the returned action.
+When `run_project_context` is returned, do not initialize workflow state manually first. Execute `workflow-project-context` with the user's provided codebase locations and project-init arguments, verify it writes `.devflow/planning/PROJECT.md`, `.devflow/planning/navigation/INDEX.md`, `.devflow/context/spec/index.md`, and `.devflow/planning/STATE.md`, then run `inspect_state.rb --json` again and continue from the returned action.
 
 ## Automatic Run Loop
 
@@ -63,7 +63,7 @@ When the invocation contains `<devflow-runtime-directive>`, run the workflow con
 4. Stop only when the inspector returns `await_user_confirmation`, `blocked`, or `workflow_complete`; also stop on an explicit user interruption or an unrecoverable tool failure.
 5. At `await_user_confirmation`, present the checkpoint and yield to the user. Resume the same loop only after an explicit confirmation and successful `devflow_transition`.
 
-Do not interpret “automatic” as permission to cross a checkpoint, weaken a gate, retry a stale revision without re-inspection, or continue after a blocked action. If context pressure requires a new turn, preserve project truth in `.planning`, finish required context synchronization, and use `/devflow resume` rather than inventing state from the conversation.
+Do not interpret “automatic” as permission to cross a checkpoint, weaken a gate, retry a stale revision without re-inspection, or continue after a blocked action. If context pressure requires a new turn, preserve project truth in `.devflow/planning`, finish required context synchronization, and use `/devflow resume` rather than inventing state from the conversation.
 
 ## Step Execution Protocol
 
@@ -105,7 +105,7 @@ When the inspector returns `await_user_confirmation`:
 5. Check artifact registry content_valid status for the listed outputs.
 6. Use `ask` to present the CP prompt, filling in the `summary_fields` from `.meta.json` data.
 7. If the user confirms, inspect the current revision and call `devflow_transition(action="confirm-checkpoint", expectedRevision=<revision>)`.
-8. If the user asks for fixes or rejects the checkpoint, keep `.planning/STATE.md` at `status: waiting_checkpoint`, inspect the current revision, call `devflow_transition(action="checkpoint-decision", decision="needs_fix", expectedRevision=<revision>)`, and route to the requested remediation.
+8. If the user asks for fixes or rejects the checkpoint, keep `.devflow/planning/STATE.md` at `status: waiting_checkpoint`, inspect the current revision, call `devflow_transition(action="checkpoint-decision", decision="needs_fix", expectedRevision=<revision>)`, and route to the requested remediation.
 
 CP skip rules:
 - CP-1, CP-API, CP-2, CP-3, CP-4: **never skip**.
@@ -137,7 +137,7 @@ If `hard_gate_mode` is `core`, a gate failure requires re-execution. In the curr
 
 When any later step discovers or introduces a change that alters external behavior, the requirement baseline must be updated first before downstream documents or code are modified.
 
-Must writeback to `.planning/requirements/baseline.md` when:
+Must writeback to `.devflow/planning/requirements/baseline.md` when:
 - New or changed user-visible behavior, notifications, failure handling, retry policy, scheduling, permissions, API contracts, or data write rules
 - Missing edge cases, compatibility requirements, historical impacts, or non-functional constraints found during execution
 - User adds/modifies requirements during tech-spec, change-plan, execution, or verification
@@ -194,7 +194,7 @@ devflow_transition(action="enter-failure-branch", expectedRevision=<revision>)
 Always obtain `<revision>` from a fresh `devflow_state(action="inspect")`. A stale
 revision is rejected without changing state, registry, or next-intent files.
 
-Checkpoint confirmation also writes the configured `.planning/.next-intent`.
+Checkpoint confirmation also writes the configured `.devflow/planning/.next-intent`.
 
 ## Control-plane recovery
 
@@ -253,19 +253,19 @@ The `.meta.json` data feeds CP prompts — e.g., CP-1 reads `baseline.meta.json`
 
 ## Initialization Rules
 
-This skill must be portable. Do not require manually-created `.planning` control files.
+This skill must be portable. Do not require manually-created `.devflow/planning` control files.
 
-If `.planning/STATE.md` is missing and project context files are also missing, route to `workflow-project-context` instead of asking for `init_state.rb`. If `.planning/STATE.md` is missing but project context files already exist, keep the existing `init_state.rb` recovery path.
+If `.devflow/planning/STATE.md` is missing and project context files are also missing, route to `workflow-project-context` instead of asking for `init_state.rb`. If `.devflow/planning/STATE.md` is missing but project context files already exist, keep the existing `init_state.rb` recovery path.
 
-If `.planning/STATE.md` contains blockers with `type: PENDING_TEMPLATE`, stop normal dispatch and report the missing depth spec template. The blocker must name the codebase, topic, matched path, missing template path, and impact.
+If `.devflow/planning/STATE.md` contains blockers with `type: PENDING_TEMPLATE`, stop normal dispatch and report the missing depth spec template. The blocker must name the codebase, topic, matched path, missing template path, and impact.
 
 Use these generators:
 
 | Script | Generates |
 |--------|-----------|
-| `init_workflow.rb` | `.planning/workflows/*.yaml` and workflow README from bundled templates. |
-| `init_state.rb` | `.planning/STATE.md` YAML front matter. |
-| `sync_artifacts.rb` | `.planning/artifacts/index.yaml` from active workflow outputs. |
+| `init_workflow.rb` | `.devflow/planning/workflows/*.yaml` and workflow README from bundled templates. |
+| `init_state.rb` | `.devflow/planning/STATE.md` YAML front matter. |
+| `sync_artifacts.rb` | `.devflow/planning/artifacts/index.yaml` from active workflow outputs. |
 
 The generated files may be project-specific instances, but their creation path must remain inside this skill.
 
@@ -273,26 +273,26 @@ The generated files may be project-specific instances, but their creation path m
 
 - Do not modify existing `workflow-*` skill behavior.
 - Auto-execute only the parallel window returned by the inspector while the runtime loop is active. Use task agents when isolation is safe; otherwise use `serial_fallback_order`.
-- Do not infer a missing workflow. If `.planning/STATE.md` has no machine-readable front matter, ask to initialize workflow state.
+- Do not infer a missing workflow. If `.devflow/planning/STATE.md` has no machine-readable front matter, ask to initialize workflow state.
 - Do not skip CP-1, CP-3, or CP-4. CP-2 can only be skipped if the active workflow config explicitly allows it.
-- Do not treat `.planning/pipeline-state.md` as the primary state source when YAML front matter exists in `.planning/STATE.md`.
+- Do not treat `.devflow/planning/pipeline-state.md` as the primary state source when YAML front matter exists in `.devflow/planning/STATE.md`.
 - Do not advance a step if its `meta_output` `.meta.json` is missing or incomplete.
 
 ## Files
 
 | File | Purpose |
 |------|---------|
-| `.planning/STATE.md` | Primary runtime state, YAML front matter + auto-generated Markdown body. |
-| `.planning/workflows/<current_flow>.yaml` | Active workflow config: step topology, CP definitions, meta_output contracts. |
+| `.devflow/planning/STATE.md` | Primary runtime state, YAML front matter + auto-generated Markdown body. |
+| `.devflow/planning/workflows/<current_flow>.yaml` | Active workflow config: step topology, CP definitions, meta_output contracts. |
 | `failure_branch.workflow_config` | Optional remediation workflow returned by the inspector. |
 | active workflow `artifact_registry.source` | Artifact status registry with content validation. |
 | `scripts/inspect_state.rb` | Deterministic state and next-action inspector. |
 | `scripts/init_workflow.rb` | Creates required workflow YAML files from bundled templates. |
-| `scripts/init_state.rb` | Creates or repairs `.planning/STATE.md` front matter. |
+| `scripts/init_state.rb` | Creates or repairs `.devflow/planning/STATE.md` front matter. |
 | `scripts/sync_artifacts.rb` | Generates artifact registry with content validation. |
 | `scripts/validate_state.rb` | Verifies STATE.md, workflow steps, dependencies, outputs, meta outputs, and artifact statuses agree before dispatch or writeback. |
 | `scripts/advance_state.rb` | State writeback + Markdown body auto-generation. |
 | `scripts/parallel_recover.rb` | Audited, CAS-guarded recovery and join for legacy lost parallel lifecycle events. |
-| `scripts/update_triage_route.rb` | Deterministically updates `.planning/requirements/{feature}/入口分诊.meta.json` route/status after clarify or wayfinder. |
+| `scripts/update_triage_route.rb` | Deterministically updates `.devflow/planning/requirements/{feature}/入口分诊.meta.json` route/status after clarify or wayfinder. |
 | `scripts/manage_lessons.rb` | Lesson candidate selector and evidence-based template writer. |
 | `templates/` | Portable workflow templates used by `init_workflow.rb`. |

package/plugins/devflow-core/skills/workflow-orchestrator/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Workflow Orchestrator"
-  short_description: "Route .planning workflows, checkpoints, remediation, and parallel windows"
-  default_prompt: "Inspect .planning/STATE.md and route the workflow safely"
+  short_description: "Route .devflow/planning workflows, checkpoints, remediation, and parallel windows"
+  default_prompt: "Inspect .devflow/planning/STATE.md and route the workflow safely"