forgetrail 0.5.15 → 0.5.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +6 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -10,7 +10,11 @@
10
10
 
11
11
  **Forge the path. Keep the trail.**
12
12
 
13
- ForgeTrail gives your next coding session a place to start. It keeps the phase, decisions, and handoff in your repository so an agent can read them when you resume. Start with Lite for a small project. You do not have to run all seven phases to try the method.
13
+ **Build software with AI, from idea to release.**
14
+
15
+ ForgeTrail guides you and your coding agent from defining a project to building a working version, improving it, and preparing it to ship. Phase guidance and review checkpoints make the next step clear; AppLedger keeps the decisions, evidence, lessons, and handoffs with the project.
16
+
17
+ The full method covers Plan, Build spine, Stabilize, Iterate, Refine, Align, and Harden. Start with Lite to agree what to build and complete the first runnable workflow. A small project does not have to run all seven phases.
14
18
 
15
19
  ForgeTrail instructs the agent to read the ledger, preserve approved decisions, and pause at approval gates. The agent must write the handoff. Those updates are not automatic. Optional hooks enforce the checks documented for their supported host.
16
20
 
@@ -45,7 +49,7 @@ MCP: `npx -y forgetrail-mcp` (0.4.2 or later finds the methodology without `FORG
45
49
 
46
50
  ## What you get
47
51
 
48
- A 7-phase playbook, a ledger in `appledger/`, and templates pre-loaded with first-party production lessons. Each project leaves decisions, lessons, and a session handoff that future work follows. Those lesson notes are not independent adoption evidence.
52
+ A development path with phase guidance, exit criteria, review checkpoints, and templates informed by first-party production lessons. ForgeTrail uses AppLedger for the project record in `appledger/`. Each project leaves decisions, lessons, and a session handoff that future work follows. Those lesson notes are not independent adoption evidence.
49
53
 
50
54
  Optional hooks in [`content/hooks/`](content/hooks/README.md) load the current phase at session start in Cursor or Claude Code, check ledger edits, and check for a session note at session stop. The agent still does the writing. Flags, MCP, and the phase table live in the [docs](https://forgetrail.dev/docs).
51
55
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "forgetrail",
3
- "version": "0.5.15",
3
+ "version": "0.5.16",
4
4
  "private": false,
5
5
  "description": "ForgeTrail: a persistent development system for building software with AI agents. CLI, Lite protocol, and methodology templates.",
6
6
  "license": "Apache-2.0",