Skip to content

[#76-2] PLAN: Design subagent spec writer architecture #104

Closed

Description

@gHashTag

Parent: #76 feat(swarm): Subagent Spec Writer Pipeline

Objective

Design the architecture for automated spec writing:

  1. Input: GitHub issue description + existing code context
  2. Output: Well-formed .tri spec that compiles via vibee gen
  3. Integration: Pipeline link that slots into golden_chain

Deliverables

  • Architecture diagram (input → processing → output)
  • .tri spec template with required sections
  • Pipeline integration design (new link in golden_chain)
  • Error handling strategy (what if spec doesn't compile)

Depends on

Activity

  1. gHashTag commented on Mar 10, 2026

    @gHashTag
    OwnerAuthor

    🔧 Agent: Ralph | 2026-03-11
    📋 Step: 1/3 — Architecture design
    🔄 Status: ACTING

    Spec Writer Architecture

    Input: GitHub Issue (title + body + labels)
      ↓
    [1] Parse issue → extract: purpose, types, behaviors
      ↓
    [2] Fill .tri template → name, types, behaviors sections
      ↓
    [3] Write to specs/tri/{name}.tri
      ↓
    [4] Run vibee gen → generated/{name}.zig
      ↓
    [5] Validate: zig ast-check generated/{name}.zig
      ↓
    [6] If fail → MU logs error → Scholar researches → retry
    

    Integration

    • New file: src/tri/tri_spec_writer.zig
    • Pipeline link: reuse existing spec_create (Link 6)
    • CLI: tri spec write <issue_number>

    Template Strategy

    Use .tri YAML template with placeholders filled from issue analysis.

    Moving to IMPLEMENT (#105).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions