aw-spec-cli 0.1.21 → 0.1.22

package/assets/.appweaver/orchestrator/workflows/aw-spec-workflow-model.orch.yaml

@@ -0,0 +1,135 @@
+# =============================================================================
+# aw-spec-workflow-model (orchestrator) — Derive Workflow Model from Feature Spec
+#
+# Stage 2 of the 4-Stage Spec-Driven UI Generation Pipeline.
+# Consumes active feature's spec.md (+ active delta-spec.md) and derives user-oriented
+# workflows (Actors, Goals, Primary Steps, Decisions, Alt Paths, Validation Failures, State Transitions).
+# Writes output artifact to `specs/<Feature>/ui/workflow-model.md`.
+#
+# Launch:
+#   /appweaver workflow-model [strategy] [guidance]
+# =============================================================================
+
+name: aw-spec-workflow-model
+description: Derive the Workflow Model (specs/<Feature>/ui/workflow-model.md) from the active feature's spec.md, describing user goals, interaction steps, decision branches, validation rules, and state transitions.
+version: 1.0.0
+agent_agnostic: true
+dialect: aw-spec.orchestrator/v1
+
+inputs:
+  user_input:
+    description: Optional guidance or specific workflow emphasis.
+    required: false
+    bind: USER_INPUT
+
+scripts:
+  actions:
+    sh:  .appweaver/scripts/bash/aw-spec-actions.sh
+    ps1: .appweaver/scripts/powershell/aw-spec-actions.ps1
+
+vars:
+  feature: ""
+  feature_dir: ""
+  feature_slug: ""
+  spec_file: ""
+  spec_exists: "false"
+  active_change: ""
+  has_change: "false"
+  domain: ""
+  prototype_root: ""
+
+workflow:
+
+  # 1. Resolve active feature and paths
+  - id: feature_paths
+    action: execute_script
+    on_error: continue
+    script: { ref: actions }
+    subcommand: feature-paths
+    outputs:
+      - { name: feature,        from: "$.feature" }
+      - { name: feature_dir,    from: "$.feature_dir" }
+      - { name: feature_slug,   from: "$.feature_slug" }
+      - { name: spec_file,      from: "$.spec_file" }
+      - { name: spec_exists,    from: "$.spec_exists" }
+      - { name: domain,         from: "$.domain" }
+      - { name: prototype_root, from: "$.prototype_root" }
+
+  - id: require_feature
+    action: verify_context
+    require_non_empty: feature_dir
+    on_empty: stop
+    on_empty_message: "No active feature selected. Run /appweaver select-feature first."
+
+  - id: require_spec
+    action: verify_context
+    require_true: spec_exists
+    on_false: stop
+    on_false_message: "No specification found for this feature. Run /appweaver specify first."
+
+  # 2. Check active change requests
+  - id: version_read
+    action: execute_script
+    on_error: continue
+    script: { ref: actions }
+    subcommand: version-read
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: active_change, from: "$.active_change" }
+      - { name: has_change,    from: "$.has_change" }
+
+  # 3. Assemble specification & template context
+  - id: ctx_workflow
+    action: build_context
+    vars:
+      feature_name: "{{feature}}"
+      feature_dir: "{{feature_dir}}"
+      user_preferences: "{{USER_INPUT}}"
+    context:
+      - "{{spec_file}}"
+      - { path: "{{feature_dir}}/changes/{{active_change}}/delta-spec.md", optional: true }
+      - { path: ".appweaver/templates/workflow-model-template.md", optional: true }
+      - { path: ".appweaver/memory/constitution.ui.md", optional: true }
+
+  # 4. Generate Workflow Model Artifact (specs/<Feature>/ui/workflow-model.md)
+  - id: generate_workflow_model
+    action: agent_generate
+    tools: "Read,Write,Edit,Bash"
+    permission_mode: acceptEdits
+    task: |
+      You are authoring Stage 2 (Workflow Model) of the 4-Stage Spec-Driven UI Pipeline for feature `{{feature_name}}`.
+
+      Target Artifact Path: `{{feature_dir}}/ui/workflow-model.md`
+
+      Instructions:
+      1. Read the feature specification (`spec.md` + active `delta-spec.md`) in context.
+      2. Identify ALL discrete user workflows required to fulfill the feature's capabilities, functional requirements (FRs), business rules (BRs), and user personas.
+      3. For EACH user workflow (WF-1, WF-2, ...), detail:
+         - **Actor / Persona**: Which role executes this flow (e.g. Project Manager, Delivery Head).
+         - **Goal**: Clear statement of user goal.
+         - **Preconditions**: Initial system state, permissions, or prerequisite conditions.
+         - **Primary Flow**: Step-by-step numbered interaction steps from start to completion.
+         - **Decision Points & Alternative Paths**: Clear branch logic (e.g. If user cancels, If user requests correction).
+         - **Validation Failures & Error Handling**: Inline system reaction when business rules or validations fail.
+         - **State Transitions**: `[Initial State]` → `[Resulting State]`.
+      4. Format the output according to `.appweaver/templates/workflow-model-template.md`.
+      5. Create the directory `{{feature_dir}}/ui/` if it does not exist, and write the authored markdown content to `{{feature_dir}}/ui/workflow-model.md`.
+
+      User Guidance:
+      {{user_preferences}}
+
+      End your final reply with a summary and a ```json fence:
+      ```json
+      {
+        "status": "ok",
+        "feature": "{{feature_name}}",
+        "workflow_model_path": "{{feature_dir}}/ui/workflow-model.md"
+      }
+      ```
+    outputs:
+      - { name: result, from: "$" }
+
+outputs:
+  feature: "{{feature}}"
+  workflow_model_path: "{{feature_dir}}/ui/workflow-model.md"
+  next: "Run /appweaver ui-model to derive the UI Model surfaces and interaction structure."