forge-orkes 0.3.13 → 0.3.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-orkes",
-  "version": "0.3.13",
+  "version": "0.3.14",
   "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/executing/SKILL.md

@@ -128,25 +128,42 @@ Attempt 1:
   1. Read error output
   2. Caused by current task?
      - YES → fix code, stage fixes, amend commit
-     - NO → mark advisory for this session, log warning, continue
+     - NO → mark advisory for this session; append to .forge/deferred-issues.md; continue
   3. Re-run command
   4. Pass → next command
   5. Fail → next attempt (up to max_retries)
 
 After max_retries exhausted:
+  → Append to .forge/deferred-issues.md
   → Log failure in execution summary
   → Continue to next task
-  → Verifying skill catches persistent failures later
 ```
 
 ### 3-Strike Integration
 Verification retries count toward the task's 3-strike limit. 2 strikes used = 1 verification retry max.
 
 ### Do NOT Fix
-- **Pre-existing failures** not from current task → mark advisory
+- **Pre-existing failures** not from current task → mark advisory; append to `.forge/deferred-issues.md`
 - **Flaky tests** passing on re-run without changes → note in summary, no strike
 - **Unrelated warnings** (deprecation, non-blocking lint) → ignore
 
+### Deferred Issues Format
+
+Append one entry per failure to `.forge/deferred-issues.md` (create if missing):
+
+```yaml
+issues:
+  - id: DI-001
+    type: test_failure | lint_failure | build_failure
+    command: "npm test"
+    summary: "HealthEndpointTest — Redis unavailable in test env"
+    first_seen: "2026-04-14"
+    milestone: "m3"
+    status: pending
+```
+
+ID = `DI-{N}` where N = next integer after existing max (or 001 if new file).
+
 ### Quick Tier
 Run all non-advisory verification commands once after commit. 1 retry max.
 

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

@@ -29,6 +29,7 @@ Read: .forge/project.yml → tech stack, framework, database, dependencies
 Read: .forge/state/milestone-{id}.yml → milestone ID and name
 Read: .forge/constitution.md → active architectural gates (if exists)
 Read: .forge/refactor-backlog.yml → existing backlog items (if any)
+Read: .forge/deferred-issues.md → pre-existing failures logged during execution (if exists)
 ```
 
 Skip by stack: no DB->SQL/NoSQL N/A, no frontend->XSS N/A, no CI/CD->Pipeline N/A.
@@ -94,7 +95,7 @@ security_audit:
 |-----------|--------|
 | **Scalability** | Synchronous blocking, missing pagination, unbounded queries, N+1, missing caching, SPOFs, hardcoded limits |
 | **Maintainability** | Files >300 lines, nesting >4, god components/classes, circular deps, dup logic |
-| **Code Health** | Dead code/unused exports, TODO/FIXME inventory, untested critical paths, stale deps |
+| **Code Health** | Dead code/unused exports, TODO/FIXME inventory, untested critical paths, stale deps, deferred issues in `.forge/deferred-issues.md` |
 | **Structural Quality** | Biz logic in UI, inconsistent patterns, missing error boundaries, API contract drift |
 
 **Rules:** Actual code, not theory. Specific files + evidence. `critical`=prod issues/blocking, `warning`=quality, `info`=improvement. Respect ADRs + constitution.
@@ -254,6 +255,13 @@ Refactoring triage (max 10): *"{N} opportunities:"*
 
 **Accept**->backlog | **Dismiss**->skip | **Accept all** | **Dismiss all**
 
+Deferred issues triage: If `.forge/deferred-issues.md` has `status: pending` items, surface them:
+*"**Test debt** ({N} pre-existing failures): 1. `{summary}` -- first seen {date}. [Accept/Dismiss/Fix-now]*"*
+
+- **Accept** → add to refactor-backlog.yml as `category: test-debt`, mark `status: triaged` in deferred-issues.md
+- **Fix-now** → route to `planning` fix mode before completing milestone
+- **Dismiss** → mark `status: dismissed` in deferred-issues.md with reason
+
 ## Step 7: Backlog + Route
 
 ### Backlog