Try
Prove ForgeTrail in one sitting: write a what, not how spec, drop it next to ForgeTrail Lite, and let your coding agent forge the path and keep the trail.
You need: any LLM chat and any coding agent that reads files.
You do not need: Node, MCP, or forgetrail on PATH.
Important: Use a new empty project folder. Do not run this inside a clone of the ForgeTrail methodology repo.
Recipe
- Copy the Genesis prompt into ChatGPT, Claude, Grok, or a local Ollama UI.
- Save the result as
docs/GENESIS.mdin a new empty folder. - Add Lite: save FORGETRAIL_LITE.md as
.forgetrail/FORGETRAIL_LITE.md, orpnpm dlx forgetrail install --lite --with-genesis-stub. - Paste this kickoff line into your coding agent:
Follow
.forgetrail/FORGETRAIL_LITE.mdas the project protocol. Treatdocs/GENESIS.mdas the product spec (what, not how). Createappledger/(manifest, profile, application record, session record) and draftdocs/PHASE_1_BRIEF.mdfrom the Genesis file, asking me only about gaps. Do not scaffold application code until I explicitly approve the Phase 1 brief.
- Approve the Phase 1 brief before any app scaffold.
What “it worked” looks like
.forgetrail/FORGETRAIL_LITE.mdis presentdocs/GENESIS.mdis presentappledger/profiles/forgetrail.yamland a session record existdocs/PHASE_1_BRIEF.mdis drafted (or clearly in progress)- The agent asked for approval before scaffolding
Stuck? Open a Try ForgeTrail checklist issue.
The same recipe lives in TRY_FORGETRAIL.md on GitHub. Short kickoff: Try. What the next session reads: Continuity.
Required on this path: the Lite file, a Genesis spec or the §5 intake, an appledger/ ledger, and a Phase 1 brief you approve. Situational: Node (only if you use the CLI), MCP, and a full template tree.
The CLI can place the Lite file and hooks. The agent creates the ledger. Those writes are not automatic.
Graduation
- Stay on Lite for small tools. Enough for many projects.
- Add MCP when you live in Cursor or Claude and want tools in the IDE.
- Full
_forgetrail/only when you need vendored templates:pnpm dlx forgetrail install.
Lite, CLI, and MCP compared: Introduction.