# AI use cases for Agent Forge (JamesBuciaIt3A/Agent-Forge)

Repo: [JamesBuciaIt3A/Agent-Forge](https://github.com/JamesBuciaIt3A/Agent-Forge) | Use cases: 4 | Page: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/

Foreman Continuum is a build playbook, contract and gate system, and decision ledger for teams that use any coding agents to design, review, and release real websites.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Build a landing page from a task contract: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/build-landing-page-from-task-contract/
- Review agent-written site changes with independent gates: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/review-agent-changes-with-independent-gates/
- Hand an unfinished site to a different coding agent: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/hand-unfinished-site-to-another-agent/
- Plan a multilingual site with locale rules in contracts: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/plan-multilingual-site-with-locale-contracts/

## How to build a landing page from a task contract with Agent Forge

Repo: [JamesBuciaIt3A/Agent-Forge](https://github.com/JamesBuciaIt3A/Agent-Forge) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Write a contract first, let one agent generate the page, then check the result against the gates.

**Who it is for:** A solo builder or small team starting a new marketing page and using a coding agent that tends to drift from the brief.

**The problem:** Agent output drifts when scope, breakpoints, and success criteria are not stated before generation starts.

**The outcome:** A page built under an explicit contract, with gate answers and a ledger entry explaining the decisions.

### Steps

1. Read the stages in the /playbook folder from discovery to deployment.
2. Write a task contract in /contracts that states scope, boundaries, breakpoints, and success criteria.
3. Pass the contract to your coding agent through a matching shim in /adapters.
4. Have a separate reviewer check the output against the acceptance criteria listed in /gates.
5. Record the decision and any deviation from the contract in /ledger.

### Prompt to paste into your agent

```text
Using the Foreman Continuum repo (JamesBuciaIt3A/Agent-Forge), read the playbook stages and write a task contract for a landing page about <target>. The contract must declare scope, breakpoints, and success criteria, saved as a file in /contracts. Verify that every success criterion can be checked by a reviewer who did not write the page.
```

### Caveat

The README describes the playbook stages and gates in prose and does not list specific file templates, so you will need to write the first contract yourself.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/build-landing-page-from-task-contract/

## How to review agent-written site changes with independent gates with Agent Forge

Repo: [JamesBuciaIt3A/Agent-Forge](https://github.com/JamesBuciaIt3A/Agent-Forge) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Check each generated change against the gate questions using a process other than the one that wrote it.

**Who it is for:** A reviewer on a team where agents produce site changes and no one can say which agent wrote a change or why.

**The problem:** Reviewers spend time rebuilding intent from commit messages because the reasons behind agent changes are not recorded.

**The outcome:** Each change has a gate review record and a ledger entry that a new contributor can read without asking the author.

### Steps

1. Open the gate checklist in /gates.
2. Find the contract that the change claims to satisfy in /contracts.
3. Check whether the artifact matches the contract's stated scope.
4. Ask a reviewer process other than the generating agent to check the acceptance criteria.
5. Hold the change until any deviation has a rationale recorded in /ledger.

### Prompt to paste into your agent

```text
Using the Foreman Continuum repo (JamesBuciaIt3A/Agent-Forge), review the artifact at <target> against the gate questions in /gates and the contract it claims to satisfy in /contracts. Output a pass or fail answer for each gate question with a one-line reason. Verify that the reviewer did not generate the artifact.
```

### Caveat

The README gives example gate questions but does not define a full checklist, so the gate pass criteria will need to be set by your team.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/review-agent-changes-with-independent-gates/

## How to hand an unfinished site to a different coding agent with Agent Forge

Repo: [JamesBuciaIt3A/Agent-Forge](https://github.com/JamesBuciaIt3A/Agent-Forge) | Difficulty: Intermediate | Time: 90 minutes | Basis: From the README

Use adapters and the ledger so a new agent continues the build without rediscovering its rules.

**Who it is for:** A team that is switching coding agents partway through a site build and wants the new agent to follow the same rules.

**The problem:** A new agent may produce output that conflicts with the earlier work because it does not know the constraints already set.

**The outcome:** The new agent continues the build under the same contracts, and gate checks confirm the output is consistent with earlier stages.

### Steps

1. Read the history in /ledger to see what was decided and why.
2. Read the contracts in /contracts that cover the remaining stages.
3. Use or write the adapter in /adapters that turns those contracts into prompts for the new agent.
4. Run the new agent on the next stage only, within the contract's stated scope.
5. Run the gates in /gates on the new output and record the result in /ledger.

### Prompt to paste into your agent

```text
Using the Foreman Continuum repo (JamesBuciaIt3A/Agent-Forge), read the ledger and the contracts for <target> and prepare a prompt for the next stage through the adapter in /adapters. The output should be the prompt text and a list of constraints it carries over from earlier stages. Verify that every constraint traces to a contract or ledger entry.
```

### Caveat

The README says adapters contain no business logic and translate contracts into prompts, but it does not list ready-made adapters for specific agents.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/hand-unfinished-site-to-another-agent/

## How to plan a multilingual site with locale rules in contracts with Agent Forge

Repo: [JamesBuciaIt3A/Agent-Forge](https://github.com/JamesBuciaIt3A/Agent-Forge) | Difficulty: Intermediate | Time: 120 minutes | Basis: From the README

Put string extraction, right-to-left rendering, and plural rules into the first contract and its gates.

**Who it is for:** A small team localizing a product website into new languages and worried about layouts breaking in translated text.

**The problem:** Translation is often added late, so layouts and formatting fail once longer or right-to-left text arrives.

**The outcome:** A first contract that names target locales, with gates for layout expansion, right-to-left rendering, plurals, and locale formatting.

### Steps

1. Read the multilingual guidance in /docs and the playbook stages in /playbook.
2. List the target locales in the first contract in /contracts.
3. Require string extraction by contract, not by accident, in the contract's scope.
4. Add gates in /gates for right-to-left rendering, pluralization categories, and locale formatting for dates, numbers, and currency.
5. Test layouts against text expansion and record the decisions in /ledger.

### Prompt to paste into your agent

```text
Using the Foreman Continuum repo (JamesBuciaIt3A/Agent-Forge), write a contract for a website that must support <target> locales. The contract must require string extraction and list gates for right-to-left rendering, pluralization, and locale formatting. Verify that each gate names a check a reviewer can run on the rendered page.
```

### Caveat

The README describes multilingual guidance as part of the playbook but does not provide localization starter kits yet, which it lists only as roadmap proposals.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/jamesbuciait3a-agent-forge/plan-multilingual-site-with-locale-contracts/