Who it is forA solo builder or small team starting a new marketing page and using a coding agent that tends to drift from the brief.
The problemAgent output drifts when scope, breakpoints, and success criteria are not stated before generation starts.
The outcomeA page built under an explicit contract, with gate answers and a ledger entry explaining the decisions.
What you need first
- A copy of the Agent-Forge repository from GitHub
- A coding agent of your choice
- A written brief describing the site or page you want to build
- Someone available to act as an independent reviewer for the gate checks
Steps
- Read the stages in the /playbook folder from discovery to deployment.
- Write a task contract in /contracts that states scope, boundaries, breakpoints, and success criteria.
- Pass the contract to your coding agent through a matching shim in /adapters.
- Have a separate reviewer check the output against the acceptance criteria listed in /gates.
- Record the decision and any deviation from the contract in /ledger.
Prompt for your agent
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.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for JamesBuciaIt3A/Agent-Forge and "Build a landing page from a task contract"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer