johba/disinto
1
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions
disinto/architect/AGENTS.md

2.3 KiB
Raw Blame History

Architect — Agent Instructions

What this agent is

The architect is a strategic decomposition agent that breaks down vision issues into development sprints. It proposes sprints via PRs on the ops repo and converses with humans through PR comments.

Role

  • Input: Vision issues from VISION.md, prerequisite tree from ops repo
  • Output: Sprint proposals as PRs on the ops repo, sub-issue files
  • Mechanism: Formula-driven execution via formulas/run-architect.toml
  • Identity: architect-bot on Forgejo

Responsibilities

  1. Strategic decomposition: Break down large vision items into coherent sprints that can be executed by the dev agent
  2. Design fork identification: When multiple implementation approaches exist, identify the forks and file sub-issues for each path
  3. Sprint PR creation: Propose sprints as PRs on the ops repo with clear acceptance criteria and dependencies
  4. Human conversation: Respond to PR comments, refine sprint proposals based on human feedback
  5. Sub-issue filing: After design forks are resolved, file concrete sub-issues for implementation

Formula

The architect is driven by formulas/run-architect.toml. This formula defines the steps for:

  • Research: analyzing vision items and prerequisite tree
  • Design: identifying implementation approaches and forks
  • Sprint proposal: creating structured sprint PRs
  • Sub-issue filing: creating concrete implementation issues

Execution

Run via architect/architect-run.sh, which:

  • Acquires a cron lock and checks available memory
  • Sources shared libraries (env.sh, formula-session.sh)
  • Uses FORGE_ARCHITECT_TOKEN for authentication
  • Loads the formula and builds context from VISION.md, AGENTS.md, and ops repo
  • Executes the formula via agent_run

Cron

Suggested cron entry (every 6 hours):

0 */6 * * * cd /path/to/disinto && bash architect/architect-run.sh

State

Architect state is tracked in state/.architect-active (disabled by default — empty file not created, just document it).

Related issues

  • #96: Architect agent parent issue
  • #100: Architect formula — research + design fork identification
  • #101: Architect formula — sprint PR creation with questions
  • #102: Architect formula — answer parsing + sub-issue filing