Configure Forge

Configure Forge

The Workspace Configurator drives this workflow. Read the workspace's forge topology and tooling preferences, then generate workspace-level prompts and agents that provide concrete forge operations.

Prerequisites: workspace.config.yaml exists with forge topology and board configuration, AI runtime is active.

Phase 1: Read Configuration

Understand the workspace's forge topology and tooling preferences.

Steps

1. Read workspace.config.yaml
2. Extract:
   • forge.topology — which providers handle repos, boards, CI, releases
   • forge.tooling.preferred — preferred tool surface (mcp, cli, api)
   • forge.tooling.<provider> — provider-specific tool settings
   • board.* — board field IDs and option IDs
   • adapters.ai-runtimes — which runtimes need generated artifacts

Output

## Context Anchors

- **Workspace:** <name>
- **Forge topology:** <repos>/<boards>/<ci>/<releases>
- **Tooling preference:** <mcp | cli>

## Configuration Detected

| Setting                 | Value   |
| ----------------------- | ------- |
| forge.topology.repos    | <value> |
| forge.topology.boards   | <value> |
| forge.tooling.preferred | <value> |

## Next Step

Confirm topology and preferences before generating.

**Approval Required:** Yes

⛔ CHECKPOINT

STOP. Do not proceed until human confirms topology and preferences.

Phase 2: Determine Artifacts

Decide what forge-specific artifacts to generate.

Artifact Matrix

Per-Runtime Output

Phase 3: Generate

Create the forge-specific workspace artifacts.

Steps

1. Generate forge operation prompts for each declared concern (issues, PRs, board)
2. Generate a forge-ops agent that knows the workspace's specific tooling
3. Include board field IDs and option IDs in generated artifacts
4. Include error handling for authentication and connectivity

⛔ CHECKPOINT

STOP. Review generated artifacts before writing.

Phase 4: Write and Verify

Write generated artifacts and verify they're correct.

Steps

1. Write generated files to appropriate locations
2. List what was generated
3. Suggest testing the generated prompts

Output

## Context Anchors

- **Workspace:** <name>
- **Forge topology:** <repos>/<boards>/<ci>/<releases>
- **Tooling preference:** <mcp | cli>

## Generated Artifacts

| File   | Purpose       |
| ------ | ------------- |
| <path> | <description> |

## Next Step

Test the generated prompts by running a forge operation.

**Approval Required:** No

Error Handling