@damphuquy/agent-init 1.0.2 → 1.0.3

package/templates/process/_seeds/task-template.md.seed

@@ -1,14 +1,26 @@
 # Task: [TASK-ID] [Task Title]
 
-<task_spec version="2.0" framework="RIPER-5">
+<task_spec version="3.0" framework="RIPER-5">
+
+<!-- ════════════════════════════════════════════
+     SECTION 0 — TASK CONTROL (master state record)
+     ════════════════════════════════════════════ -->
+<task_control>
+  <status>BACKLOG</status>  <!-- BACKLOG | ACTIVE | BLOCKED | REVIEW | COMPLETED -->
+  <spec_level>S1</spec_level>  <!-- S0=sketch | S1=defined | S2=verified | S3=locked -->
+  <risk>MEDIUM</risk>  <!-- LOW | MEDIUM | HIGH -->
+  <working_mode>PAIR</working_mode>  <!-- MANUAL | PAIR | DELEGATED | DIAGNOSE-ONLY -->
+  <current_phase>RESEARCH</current_phase>  <!-- RESEARCH | INNOVATE | PLAN | EXECUTE | REVIEW -->
+  <owner>@engineer</owner>
+  <decision_owner>@engineer</decision_owner>
+  <created></created>
+  <last_updated></last_updated>
+</task_control>
 
-<status>
-  <phase>PLANNING</phase> <!-- RESEARCHING | PLANNING | PRODUCING | EVALUATING | RECONCILED | COMPLETED -->
-  <state>IN_PROGRESS</state>
-  <assignee>@agent_or_human</assignee>
-</status>
+---
 
 ## 1. Specification (Pillar 1: Task / Spec)
+
 <specification>
   <goal>
     [Target outcome, business value, or functional capability.]
@@ -22,8 +34,12 @@
     [Expected behavior once the change is complete.]
   </expected_behavior>
 
+  <actor_authorization>
+    [Who initiates this action, under what authorization context.]
+  </actor_authorization>
+
   <invariants>
-    - [Invariant 1 — Conditions that must remain true.]
+    - [Invariant 1 — Conditions that must remain true throughout and after this change.]
   </invariants>
 
   <out_of_scope>
@@ -31,62 +47,149 @@
   </out_of_scope>
 
   <acceptance_criteria>
-    - [ ] [AC-1: Verifiable functional behavior with explicit input and expected output]
-    - [ ] [AC-2: Edge cases, validation rules, or error handling]
-    - [ ] [AC-3: Automated tests added/updated and passing]
+    - [ ] AC-1: [Verifiable functional behavior with explicit input and expected output]
+    - [ ] AC-2: [Edge cases, validation rules, or error handling]
+    - [ ] AC-3: [Automated tests added/updated and passing]
   </acceptance_criteria>
 </specification>
 
 ---
 
 ## 2. Context Boundaries (Pillar 2: Context)
+
 <context_boundaries>
   <target_files>
     - `src/[path/to/file]` — [Planned modification]
     - `tests/[path/to/test_file]` — [Target assertions and test fixtures]
   </target_files>
+
+  <source_of_truth>
+    <requirement>[Link to requirement or spec]</requirement>
+    <architecture>[Link to architecture doc or ADR]</architecture>
+    <existing_behavior>[Test file or code path that proves current behavior]</existing_behavior>
+    <tests>[Primary test suite path]</tests>
+  </source_of_truth>
 </context_boundaries>
 
 ---
 
-## 3. RIPER-5 Execution Plan (Pillar 4: Loop)
+## 3. Verification Strategy
+
+<!-- Evidence required to close each AC before marking COMPLETED -->
+<verification_strategy>
+
+| AC / Risk | Evidence required | Verifier |
+|---|---|---|
+| AC-1 | | |
+| AC-2 | | |
+| AC-3 | | |
+
+</verification_strategy>
+
+---
+
+## 4. Decisions
+
+<decisions>
+  <approved_decisions>
+    <!-- Decisions that are final and must not be re-opened by the agent -->
+    <!-- | ID | Decision | Rationale | Owner | -->
+  </approved_decisions>
+
+  <open_decisions>
+    <!-- Decisions that still need a human to choose; agent must HALT on these -->
+    <!-- | ID | Question | Why it matters | Owner | Blocking? | -->
+  </open_decisions>
+</decisions>
+
+---
+
+## 5. RIPER-5 Execution Plan (Pillar 4: Loop)
+
 <execution_plan>
-  <phase name="Research">
+  <phase name="Research" order="1">
+    <!-- READ-ONLY. No source modifications. No implementation decisions. -->
     - [ ] Ingest task spec, domain invariants, and out-of-scope boundaries.
     - [ ] Read corresponding tests and port interfaces.
+    - [ ] Establish execution flow, boundaries, and source-of-truth conflicts.
+    - [ ] Produce/update `research.md` artifact.
+    <gate id="G0" label="Research Complete">
+      - [ ] Current behavior understood and documented.
+      - [ ] Execution flow traced.
+      - [ ] No unresolved research blocker.
+    </gate>
   </phase>
 
-  <phase name="Innovate & Plan">
-    - [ ] Step 1: [Design domain models / port contracts]
-    - [ ] Step 2: [Formulate test strategy and edge cases]
+  <phase name="Innovate" order="2">
+    <!-- READ-ONLY. Present 2-3 viable options. Do not decide unilaterally. -->
+    - [ ] Generate 2–3 alternative approaches with trade-off matrix.
+    - [ ] Produce `decision.md` artifact.
+    <gate id="G1" label="Gate 1 — Decision Approved">
+      - [ ] Options reviewed by engineer.
+      - [ ] Selected option recorded in `decision.md`.
+      - [ ] No blocking business/schema/security decision remains open.
+      <approved_by></approved_by>
+      <approved_date></approved_date>
+    </gate>
   </phase>
 
-  <phase name="Produce">
-    - [ ] Step 1: [Implement core logic with strict typing]
-    - [ ] Step 2: [Implement automated unit/integration tests]
+  <phase name="Plan" order="3">
+    <!-- Plan artifacts only. No source-code changes. -->
+    - [ ] Decompose into vertical slices with verifiers and rollback points.
+    - [ ] Populate `plan.md` with scope contract and verification matrix.
+    <gate id="G2" label="Gate 2 — Plan Approved">
+      - [ ] Every slice has a verifier.
+      - [ ] Allowed/forbidden file scope is defined.
+      - [ ] Rollback point defined per slice.
+      - [ ] Stop conditions defined.
+      - [ ] Engineer approved.
+      <approved_by></approved_by>
+      <approved_date></approved_date>
+    </gate>
   </phase>
 
-  <phase name="Evaluate">
-    - [ ] Execute focused tests and full validation suite.
+  <phase name="Execute" order="4">
+    <!-- Read/write only within approved scope. One slice at a time. -->
+    - [ ] Implement each slice atomically.
+    - [ ] Run verifier after each slice.
+    - [ ] Inspect diff after each slice.
+    - [ ] Update `state.md` after each slice.
   </phase>
 
-  <phase name="Reconcile & Review">
-    - [ ] Review `git diff` for zero unwanted changes or debug statements.
-    - [ ] Verify all Acceptance Criteria are satisfied (`- [x]`).
-    - [ ] Mark phase as COMPLETED.
+  <phase name="Review" order="5">
+    <!-- READ-ONLY. May run verification commands. No code fixes during review. -->
+    - [ ] Review full diff, behavior, architecture, data, security, regression.
+    - [ ] Produce `review.md` with findings and verification matrix.
+    <gate id="G3" label="Gate 3 — Review Passed">
+      - [ ] All AC verified with evidence.
+      - [ ] Residual risk accepted.
+      - [ ] Review decision: PASS | CHANGES_REQUIRED | BLOCKED.
+      - [ ] Ready for handoff.
+      <approved_by></approved_by>
+      <approved_date></approved_date>
+    </gate>
   </phase>
 </execution_plan>
 
 ---
 
-## 4. Guardrails & Escalation (Pillar 3 & 4: Harness)
+## 6. Guardrails & Escalation (Pillar 3 & 4: Harness)
+
 <guardrails>
-  <open_decisions>
-    <!-- Log any technical trade-offs or items requiring human guidance here -->
-  </open_decisions>
+  <stop_conditions>
+    <!-- Agent must HALT and request human guidance on any of these -->
+    - Missing business or policy decision.
+    - Public API / DB schema change not declared in this spec.
+    - New external dependency not declared in this spec.
+    - Security policy change required.
+    - Scope expansion beyond `<out_of_scope>`.
+    - Retry budget exhausted on a recurring failure.
+  </stop_conditions>
 
   <retry_budget max_attempts="3">
     Maximum 3 consecutive attempts per distinct failure symptom before halting.
+    Never suppress errors with flags (e.g. `# type: ignore`, `eslint-disable`).
+    If exhausted, log into `<open_decisions>` and halt.
   </retry_budget>
 </guardrails>
 

package/templates/process/context/all-context.md

@@ -17,7 +17,7 @@
   <group id="seeds">
     <title>Seeds & Archetypes Guide</title>
     <path>[`../_seeds/_GUIDE.md`](../_seeds/_GUIDE.md)</path>
-    <scope>Scaffolding seeds for tasks, programs, and context groups</scope>
+    <scope>Scaffolding seeds for tasks, research, decisions, plans, state, reviews, handoffs, and programs. Full artifact chain and instantiation commands.</scope>
   </group>
 
   <group id="protocols">

package/templates/.agents/name_rule.md

@@ -1,3 +0,0 @@
-# name rule
-
-Never use leading underscores `_` for function or method names. Write flat, clean, public functions with self-explanatory names unless explicitly asked.