forge-orkes 0.5.0 → 0.5.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-orkes",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Set up the Forge meta-prompting framework for Claude Code in your project",
   "bin": {
     "create-forge": "./bin/create-forge.js"

package/template/.claude/skills/discussing/SKILL.md

@@ -18,9 +18,28 @@ Structured conversation: approach, trade-offs, decisions. Clarity, not artifacts
 ## Boundaries
 
 - No plans or code
-- Writes only `context.md` (at convergence, before handoff)
+- Writes `context.md` progressively (after each confirmed decision, not just at handoff)
 - No phase/plan required
 
+## Progressive Persistence
+
+**Decisions persist immediately.** After each user response that confirms a decision, write it to `.forge/context.md` right away. Don't accumulate in working memory.
+
+### Rules
+
+1. **Create `context.md` on first decision** if it doesn't exist (from template `.forge/templates/context.md`)
+2. **Scope by milestone.** Add decisions under `### M{id} — {name} (drafting)` inside `## Locked Decisions`
+3. **Append, don't rewrite.** Each confirmed decision → append one `- **[Topic]**: [Decision]. Reason: [Why]` line
+4. **Deferred ideas too.** User says "not now" / "later" / "skip" → append to `## Deferred Ideas` immediately
+5. **Discretion areas too.** Left to agent judgment → append to `## Discretion Areas` immediately
+6. **Phase Handoff promotes.** Rename `(drafting)` → `(locked {date})` at convergence. No content change needed — decisions are already written
+
+### Why
+
+Sessions `/clear` or die mid-discussion. Previous behavior: decisions lived only in conversation memory until Step 5 convergence. If session ended before convergence, all Q&A answers vanished. Planning would start from scratch.
+
+Now: any `/clear` preserves everything decided so far. Worst case on interruption = last answer lost, not all answers.
+
 ## Pre-Planning Discussion
 
 ### Step 0: Load Context
@@ -60,6 +79,8 @@ Brief context paragraph from research.
 
 Surface 3-5 decisions that matter.
 
+**After each user response:** write confirmed decisions to `context.md` immediately (see Progressive Persistence).
+
 ### Step 2: Facilitate, Don't Dictate
 
 Help user think deeper, don't push preference. `AskUserQuestion` for decisions; prose for open-ended.
@@ -89,6 +110,8 @@ AskUserQuestion:
 
 Open-ended via prose: *"Tried before?" / "Must-haves or must-nots?"* 1-2 at a time.
 
+**After each user response:** write confirmed decisions/constraints to `context.md` immediately.
+
 ### Step 4: Functionality Distillation
 
 Per feature, force behavioral clarity. Surface assumptions + edge cases.
@@ -103,6 +126,8 @@ Per feature, force behavioral clarity. Surface assumptions + edge cases.
 
 Not all 5 mechanically. 2-3 questions, deeper on uncertainty. `AskUserQuestion` for discrete; prose to explain.
 
+**After each user response:** write confirmed behavioral decisions to `context.md` immediately.
+
 Example -- L3:
 ```
 question: "When the enrichment API is down, what should the system do?"
@@ -223,11 +248,11 @@ Re-plan? Route to `planning` with summary.
 
 After convergence:
 
-1. **Write `context.md`** -- Create/update `.forge/context.md` from template (`.forge/templates/context.md`). Populate:
-   - **Locked Decisions**: all confirmed decisions from Steps 1-5
-   - **Deferred Ideas**: anything explicitly deferred
-   - **Discretion Areas**: topics left to agent judgment
-   - **Needs Resolution**: unresolved items (if any)
+1. **Promote decisions in `context.md`** -- Rename milestone heading from `(drafting)` → `(locked {date})`. Decisions already written progressively — just finalize:
+   - Verify all confirmed decisions present under `## Locked Decisions`
+   - Verify deferred items under `## Deferred Ideas`
+   - Verify discretion areas under `## Discretion Areas`
+   - Add any unresolved items to `## Needs Resolution`
    - If `context.md` already exists (post-planning discussion), update relevant sections + log amendments
 2. **Update state** -- `current.status` = `planning` (`architecting` for Full) in milestone yml
 3. **Recommend clear:**