@christianmaf80/agentic-workflow 1.6.0-beta.1 → 1.7.0-beta.1

package/dist/templates/brief.md

@@ -20,15 +20,15 @@ First line of the document:
 
 ---
 
-## 2. The 5 Mandatory Questions
+## 2. The 5 Mandatory Questions (Dynamic)
 
 | # | Question (formulated by architect) | Answer (from developer) |
 |---|-----------------------------------|-------------------------|
-| 1 | | |
-| 2 | | |
-| 3 | | |
-| 4 | | |
-| 5 | | |
+| 1 | <dynamic question based on task description> | |
+| 2 | <dynamic question based on task description> | |
+| 3 | <dynamic question based on task description> | |
+| 4 | <dynamic question based on task description> | |
+| 5 | <dynamic question based on task description> | |
 
 ---
 

package/dist/templates/init.md

@@ -16,6 +16,13 @@ First line of the document:
 ```yaml
 bootstrap:
   done: true
+language:
+  confirmed: false
+developer:
+  name: ""
+strategy: ""
+task:
+  description: ""
 roles:
   architect: {{architectAgentId}}
 constitution:

package/dist/templates/research.md

@@ -24,6 +24,18 @@ First line of the document:
 
 ---
 
+## Clarifications (5 Mandatory Questions, Dynamic)
+
+| # | Question (formulated by architect) | Answer (from developer) |
+|---|-----------------------------------|-------------------------|
+| 1 | <dynamic question based on task description> | |
+| 2 | <dynamic question based on task description> | |
+| 3 | <dynamic question based on task description> | |
+| 4 | <dynamic question based on task description> | |
+| 5 | <dynamic question based on task description> | |
+
+---
+
 ## 2. Detected Needs
 - Technical requirements identified by the architect-agent
 - Assumptions and limits

package/dist/workflows/init.md

@@ -19,41 +19,39 @@ blocking: true
 
 ## Objective (ONLY)
 - Activate the **architect-agent** role.
-- Load the minimum bootstrap indices.
-- Load the constitution rules into context.
-- Detect the conversation language and confirm explicitly.
-- **Select the lifecycle strategy (Long/Short)**.
+- Load the prebuilt bootstrap bundle (constitutions + indexes + core roles).
+- Capture developer language, name, strategy, and first task description.
 - Create the **task candidate** artifact `init.md`.
 
 ## Mandatory Steps
-1. **Reasoning (MANDATORY)**
-   - Explain to the developer what will be done in this phase and why.
-2. Use the `bootstrap_context` tool to load the prebuilt core bootstrap bundle plus local indices in a single step.
-3. Save the bundle output to `.agent/artifacts/candidate/bootstrap.md`.
-4. Detect preferred language and ask for explicit confirmation (**YES**).
-5. Select lifecycle strategy (**Long** or **Short**).
-6. Create the `init.md` artifact using `templates.init`.
-7. Evaluate Gate.
+1. Use the `bootstrap_context` tool to load the prebuilt core bootstrap bundle plus local indices in a single step.
+2. Save the bundle output to `.agent/artifacts/candidate/bootstrap.md`.
+3. Ask the developer to confirm language (**YES**).
+4. Ask the developer for their preferred name (used in all future responses).
+5. Ask the developer to choose lifecycle strategy: **short (fast)** or **long**.
+6. Ask for the first task description (1-3 sentences).
+7. Create the `init.md` artifact using `templates.init`.
+8. Evaluate Gate.
    - The developer **MUST** explicitly confirm with a **YES**.
 
 ## Output (REQUIRED)
 - Created artifact: `artifacts.candidate.init` (from `templates.init`).
 - Created artifact: `artifacts.candidate.bootstrap` (bundle from `bootstrap_context`).
 
-## Reasoning (MANDATORY)
-- Before executing, the architect-agent must explain to the developer what will be done and why.
-- No document is required for this step.
-
 ## Pass
 - `init.md` is created from `templates.init`.
-- Language is confirmed and strategy is set.
+- Language is confirmed, developer name is captured, strategy is set, and task description exists.
 - `bootstrap.md` exists and contains the bundle.
 
 ## Gate (REQUIRED)
 Requirements (all mandatory):
 1. `artifacts.candidate.init` exists.
 2. `artifacts.candidate.bootstrap` exists.
-3. In `init.md` YAML: `language.confirmed == true` and `strategy` is defined.
+3. In `init.md` YAML:
+   - `language.confirmed == true`
+   - `developer.name` is defined
+   - `strategy` is defined
+   - `task.description` is defined
 4. The developer has explicitly approved with **YES**.
 
 If Gate FAIL:

package/dist/workflows/tasklifecycle-long/phase-1-research.md

@@ -70,11 +70,15 @@ blocking: true
    - `task.md` contains acceptance criteria
    - If fails → go to **Step 8 (FAIL)**.
 
-2. Load research template (architect-agent)
+2. Ask 5 mandatory clarification questions (architect-agent)
+   - Generate them dynamically from the task description to clarify scope, inputs, outputs, constraints, and success criteria.
+   - Capture answers in `research.md` under a `clarifications` section.
+
+3. Load research template (architect-agent)
    - Load `templates.research`
    - If it doesn't exist or cannot be read → go to **Step 8 (FAIL)**.
 
-3. **Delegate to researcher-agent (MANDATORY)**
+4. **Delegate to researcher-agent (MANDATORY)**
    > ⚠️ **PERMANENT RULE**: The `architect-agent` **CANNOT** create the research report.
    > The `researcher-agent` is the **only authorized agent** to create `research.md`.
 
@@ -98,7 +102,7 @@ blocking: true
      - Official or prestigious sources
    - Hand back control to the `architect-agent` upon completion
 
-4. Request developer approval (MANDATORY, via console)
+5. Request developer approval (MANDATORY, via console)
    - The developer **MUST** issue a binary decision:
      - **YES** → Approved
      - **NO** → Rejected
@@ -112,7 +116,7 @@ blocking: true
      ```
    - If `decision != YES` → go to **Step 8 (FAIL)**.
 
-5. PASS
+6. PASS
    - Update `.agent/artifacts/<taskId>-<taskTitle>/task.md` (using prefix):
      - Mark Phase 1 as completed
      - Set `task.lifecycle.phases.phase-1-research.validated_at = <ISO-8601>`

package/dist/workflows/tasklifecycle-short/short-phase-1-brief.md

@@ -34,6 +34,7 @@ blocking: true
    - `task.strategy == "short"`.
 
 2. Execute 5 mandatory questions.
+   - Generate them dynamically from the task description to clarify scope, inputs, outputs, constraints, and success criteria.
 
 3. Complexity analysis.
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@christianmaf80/agentic-workflow",
-    "version": "1.6.0-beta.1",
+    "version": "1.7.0-beta.1",
     "description": "Portable agentic workflow orchestration system with strict identity and gate discipline",
     "type": "module",
     "main": "dist/index.js",