arggon-harness 0.1.2 → 0.2.0

package/src/templates/hybrid/tasks.yaml

@@ -0,0 +1,103 @@
+# Hybrid Workflow Tasks Template
+#
+# Supports both standard task patterns and TDD RED→GREEN→REFACTOR tasks.
+#
+# Use STANDARD tasks when:
+#   - Implementing well-understood features with clear requirements
+#   - Making infrastructure/config/build changes
+#   - Writing documentation or non-code artifacts
+#   - Making small, low-risk changes
+#
+# Use TDD tasks (with tdd_phase) when:
+#   - Implementing core business logic
+#   - Making changes with high regression risk
+#   - Building new APIs or data processing pipelines
+#   - Refactoring complex code
+#
+# Standard tasks use: id, group, description, depends_on, complexity,
+#   estimated_minutes, spec_refs, affected_files, acceptance, status
+#
+# TDD tasks add: tdd_phase: 'red' | 'green' | 'refactor'
+#
+# You can mix both patterns in the same task list.
+# Standard tasks typically go first (setup), then TDD loops for each behavior.
+
+workflow: hybrid
+
+agent:
+  critical_path:
+    - t1
+    - t2
+    - t3
+    - t4
+  total_estimated_minutes: 200
+
+tasks:
+  # ── Standard task example (infrastructure/setup) ──
+  - id: t1
+    group: Setup
+    description: Configure [dependency/infrastructure]
+    depends_on: []
+    complexity: low
+    estimated_minutes: 20
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - [path/to/config/file]
+    acceptance:
+      - [dependency] is configured and working
+      - Configuration follows project conventions
+    status: pending
+
+  # ── TDD loop: RED → GREEN → REFACTOR for [behavior-1] ──
+  - id: t2
+    group: "TDD: RED"
+    description: Write failing test for [behavior-1]
+    depends_on:
+      - t1
+    complexity: low
+    estimated_minutes: 15
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - test/[test-file].test.ts
+    acceptance:
+      - Test compiles and runs
+      - Test fails with expected message
+    tdd_phase: red
+    status: pending
+
+  - id: t3
+    group: "TDD: GREEN"
+    description: Implement minimal code to pass [behavior-1] test
+    depends_on:
+      - t2
+    complexity: low
+    estimated_minutes: 20
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - src/[implementation].ts
+    acceptance:
+      - All existing tests still pass
+      - New test from t2 now passes
+    tdd_phase: green
+    status: pending
+
+  - id: t4
+    group: "TDD: REFACTOR"
+    description: Refactor [behavior-1] implementation and tests
+    depends_on:
+      - t3
+    complexity: medium
+    estimated_minutes: 25
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - src/[implementation].ts
+      - test/[test-file].test.ts
+    acceptance:
+      - All tests still pass
+      - Code is clean and follows conventions
+    tdd_phase: refactor
+    status: pending

package/src/templates/spec-driven/design-tech.yaml

@@ -0,0 +1,42 @@
+# Design Template
+#
+# Instructions:
+# - Focus on HOW to implement
+# - Include alternatives considered
+# - Only create if change is complex enough
+
+id: <change-name>
+schema: <schema-name>
+
+agent:
+  context_files:
+    - <relevant files>
+  affected_paths:
+    - <paths affected>
+
+body:
+  context: |
+    <Background, current state, constraints>
+  
+  goals:
+    - <What this design achieves>
+    - <Another goal>
+  
+  non_goals:
+    - <What's explicitly out of scope>
+    - <Another non-goal>
+  
+  decisions:
+    - title: <decision title>
+      approach: |
+        <Chosen approach and rationale>
+      alternatives: |
+        <Alternatives considered and why not chosen>
+    
+    - title: <another decision>
+      approach: |
+        <approach>
+  
+  risks:
+    - <Risk and mitigation strategy>
+    - <Another risk>

package/src/templates/spec-driven/proposal.yaml

@@ -0,0 +1,43 @@
+# Proposal Template
+# 
+# Instructions:
+# - Replace <placeholders> with actual values
+# - Remove comment lines (starting with #) before saving
+# - Keep the structure intact
+
+id: <change-name-kebab-case>
+schema: <schema-name>
+created: <YYYY-MM-DD>
+status: active
+
+agent:
+  priority: <low|medium|high>
+  context_files:
+    - <file1.ts>
+    - <file2.ts>
+  affected_paths:
+    - <src/path/**>
+  hints:
+    - <implementation hint>
+
+body:
+  why: |
+    <1-3 sentences explaining the problem and why this change is needed>
+  
+  what_changes:
+    - <bullet point describing a change>
+    - <another change>
+  
+  capabilities:
+    new:
+      - id: <capability-id>
+        description: <what this capability does>
+    modified:
+      - id: <existing-capability-id>
+        description: <what changed>
+  
+  impact:
+    - path: <src/file.ts>
+      change: <what changes in this file>
+    - path: <src/another.ts>
+      change: <description>

package/src/templates/spec-driven/schema.yaml

@@ -0,0 +1,32 @@
+name: spec-driven
+version: 1
+description: Standard spec-driven workflow with proposal, specs, design, and tasks
+
+artifacts:
+  - id: proposal
+    generates: proposal.yaml
+    description: Change proposal with why, what, and impact
+    template: proposal.yaml
+    requires: []
+
+  - id: specs
+    generates: specs/*.yaml
+    description: Delta specifications for each capability with requirement scenarios
+    template: spec.yaml
+    requires: [proposal]
+
+  - id: design-tech
+    generates: design-tech.yaml
+    description: Technical design with architecture decisions, alternatives, and risks
+    template: design-tech.yaml
+    requires: [proposal]
+
+  - id: tasks
+    generates: tasks.yaml
+    description: Implementation task list with dependencies and acceptance criteria
+    template: tasks.yaml
+    requires: [specs, design-tech]
+
+apply:
+  requires: [tasks]
+  tracks: tasks.yaml

package/src/templates/spec-driven/spec.yaml

@@ -0,0 +1,56 @@
+# Delta Spec Template
+#
+# Instructions:
+# - One file per capability
+# - Use operations: add, modify, remove, rename
+# - Each requirement must have at least one scenario
+# - Add verify blocks for testable assertions
+
+capability: <capability-id>
+version: 1
+
+agent:
+  related_specs:
+    - <other-capability>
+  affected_paths:
+    - <src/auth/**>
+
+operations:
+  - op: add
+    requirement:
+      id: <requirement-id>
+      description: |
+        The system SHALL <behavior description>.
+      scenarios:
+        - id: <scenario-id>
+          given:
+            - <precondition>
+          when:
+            - <action or event>
+          then:
+            - <expected outcome>
+          verify:
+            - type: assertion
+              code: "<testable assertion>"
+  
+  # Example modify operation:
+  # - op: modify
+  #   requirement:
+  #     id: <existing-requirement-id>
+  #     description: |
+  #       <complete updated requirement>
+  #     scenarios:
+  #       - id: <scenario-id>
+  #         given: [...]
+  #         when: [...]
+  #         then: [...]
+  
+  # Example remove operation:
+  # - op: remove
+  #   requirement:
+  #     id: <requirement-to-remove>
+  
+  # Example rename operation:
+  # - op: rename
+  #   from: <old-id>
+  #   to: <new-id>

package/src/templates/tdd/design-tech.yaml

@@ -0,0 +1,42 @@
+# Design Template
+#
+# Instructions:
+# - Focus on HOW to implement
+# - Include alternatives considered
+# - Only create if change is complex enough
+
+id: <change-name>
+schema: <schema-name>
+
+agent:
+  context_files:
+    - <relevant files>
+  affected_paths:
+    - <paths affected>
+
+body:
+  context: |
+    <Background, current state, constraints>
+  
+  goals:
+    - <What this design achieves>
+    - <Another goal>
+  
+  non_goals:
+    - <What's explicitly out of scope>
+    - <Another non-goal>
+  
+  decisions:
+    - title: <decision title>
+      approach: |
+        <Chosen approach and rationale>
+      alternatives: |
+        <Alternatives considered and why not chosen>
+    
+    - title: <another decision>
+      approach: |
+        <approach>
+  
+  risks:
+    - <Risk and mitigation strategy>
+    - <Another risk>

package/src/templates/tdd/proposal.yaml

@@ -0,0 +1,43 @@
+# Proposal Template
+# 
+# Instructions:
+# - Replace <placeholders> with actual values
+# - Remove comment lines (starting with #) before saving
+# - Keep the structure intact
+
+id: <change-name-kebab-case>
+schema: <schema-name>
+created: <YYYY-MM-DD>
+status: active
+
+agent:
+  priority: <low|medium|high>
+  context_files:
+    - <file1.ts>
+    - <file2.ts>
+  affected_paths:
+    - <src/path/**>
+  hints:
+    - <implementation hint>
+
+body:
+  why: |
+    <1-3 sentences explaining the problem and why this change is needed>
+  
+  what_changes:
+    - <bullet point describing a change>
+    - <another change>
+  
+  capabilities:
+    new:
+      - id: <capability-id>
+        description: <what this capability does>
+    modified:
+      - id: <existing-capability-id>
+        description: <what changed>
+  
+  impact:
+    - path: <src/file.ts>
+      change: <what changes in this file>
+    - path: <src/another.ts>
+      change: <description>

package/src/templates/tdd/schema.yaml

@@ -0,0 +1,32 @@
+name: tdd
+version: 1
+description: Test-driven development with RED-GREEN-REFACTOR vertical slices
+
+artifacts:
+  - id: proposal
+    generates: proposal.yaml
+    description: Change proposal with testable acceptance criteria
+    template: proposal.yaml
+    requires: []
+
+  - id: specs
+    generates: specs/*.yaml
+    description: Requirements with Gherkin scenarios and test verification blocks
+    template: spec.yaml
+    requires: [proposal]
+
+  - id: design-tech
+    generates: design-tech.yaml
+    description: Technical design with testability decisions and interface contracts
+    template: design-tech.yaml
+    requires: [specs]
+
+  - id: tasks
+    generates: tasks.yaml
+    description: Vertical slice tasks organized as RED-GREEN-REFACTOR per behavior
+    template: tasks.yaml
+    requires: [specs, design-tech]
+
+apply:
+  requires: [tasks]
+  tracks: tasks.yaml

package/src/templates/tdd/spec.yaml

@@ -0,0 +1,56 @@
+# Delta Spec Template
+#
+# Instructions:
+# - One file per capability
+# - Use operations: add, modify, remove, rename
+# - Each requirement must have at least one scenario
+# - Add verify blocks for testable assertions
+
+capability: <capability-id>
+version: 1
+
+agent:
+  related_specs:
+    - <other-capability>
+  affected_paths:
+    - <src/auth/**>
+
+operations:
+  - op: add
+    requirement:
+      id: <requirement-id>
+      description: |
+        The system SHALL <behavior description>.
+      scenarios:
+        - id: <scenario-id>
+          given:
+            - <precondition>
+          when:
+            - <action or event>
+          then:
+            - <expected outcome>
+          verify:
+            - type: assertion
+              code: "<testable assertion>"
+  
+  # Example modify operation:
+  # - op: modify
+  #   requirement:
+  #     id: <existing-requirement-id>
+  #     description: |
+  #       <complete updated requirement>
+  #     scenarios:
+  #       - id: <scenario-id>
+  #         given: [...]
+  #         when: [...]
+  #         then: [...]
+  
+  # Example remove operation:
+  # - op: remove
+  #   requirement:
+  #     id: <requirement-to-remove>
+  
+  # Example rename operation:
+  # - op: rename
+  #   from: <old-id>
+  #   to: <new-id>

package/src/templates/tdd/tasks.yaml

@@ -0,0 +1,77 @@
+# TDD Workflow Tasks Template
+#
+# Tasks are structured around the RED → GREEN → REFACTOR loop.
+# Each vertical slice of behavior produces three tasks:
+#
+#   RED:     Write a failing test that defines the desired behavior
+#   GREEN:   Write the minimal implementation to pass the test
+#   REFACTOR: Clean up both test and implementation
+#
+# The tdd_phase field marks which phase each task belongs to.
+# Tasks without a tdd_phase use the standard task format.
+
+workflow: tdd
+
+agent:
+  critical_path:
+    - t1
+    - t2
+    - t3
+  total_estimated_minutes: 120
+
+tasks:
+  - id: t1
+    group: RED
+    description: Write failing test for [behavior]
+    depends_on: []
+    complexity: low
+    estimated_minutes: 15
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - test/[path-to-test-file].test.ts
+    acceptance:
+      - Test compiles and runs
+      - Test fails with expected error/message
+      - Test name describes the expected behavior
+    tdd_phase: red
+    status: pending
+
+  - id: t2
+    group: GREEN
+    description: Implement minimal code to pass [behavior] test
+    depends_on:
+      - t1
+    complexity: low
+    estimated_minutes: 20
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - src/[path-to-implementation].ts
+    acceptance:
+      - All existing tests still pass
+      - New test from t1 now passes
+      - Implementation is minimal (no premature optimization)
+      - No new failing tests introduced
+    tdd_phase: green
+    status: pending
+
+  - id: t3
+    group: REFACTOR
+    description: Refactor [behavior] implementation and tests
+    depends_on:
+      - t2
+    complexity: medium
+    estimated_minutes: 25
+    spec_refs:
+      - [capability-id]/REQ-[requirement-id]
+    affected_files:
+      - src/[path-to-implementation].ts
+      - test/[path-to-test-file].test.ts
+    acceptance:
+      - All tests still pass
+      - Code follows project conventions
+      - No duplicated logic
+      - Names and structure are clean
+    tdd_phase: refactor
+    status: pending