feed-the-machine 1.4.1 → 1.5.0

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.
@@ -174,22 +174,35 @@ Parallel waves:
174
174
  Final: Task [N] (integration/cleanup)
175
175
  ```
176
176
 
177
- ### Phase 1.5: Documentation Layer Bootstrap
177
+ ### Phase 1.5: Documentation Layer Bootstrap (MANDATORY)
178
178
 
179
- Before dispatching any agents, check if the project has the required documentation layer. If any of these files are missing, create them.
179
+ **This phase is non-skippable.** The documentation layer is required for ftm-verify to assess plan completion, for ftm-codex-gate to detect intent conflicts, and for agents to update docs as they work. Without it, every downstream verification step is degraded.
180
180
 
181
- **Check for and create if missing:**
182
- 1. **INTENT.md** (project root) — If missing, bootstrap from the plan's Vision and Architecture Decisions sections. Use the ftm-intent skill's root template format.
183
- 2. **ARCHITECTURE.mmd** (project root)If missing, bootstrap by scanning the codebase for modules and their import relationships. Use the ftm-diagram skill's root template format.
184
- 3. **STYLE.md** (project root) — If missing, copy from `~/.claude/skills/ftm-executor/references/STYLE-TEMPLATE.md` into the project root.
185
- 4. **DEBUG.md** (project root) — If missing, create with a header:
181
+ Before dispatching any agents, check if the project has the required documentation layer. If any of these files are missing, create them. If they already exist, verify they're non-empty and well-formed.
182
+
183
+ **Required documentation filescreate if missing:**
184
+ 1. **INTENT.md** (project root) — Bootstrap from the plan's Vision and Architecture Decisions sections. Use the ftm-intent skill's root template format. Must include: Vision, Architecture Decisions table, Module Map.
185
+ 2. **ARCHITECTURE.mmd** (project root) — Bootstrap by scanning the codebase for modules and their import relationships. Use the ftm-diagram skill's root template format. Must have at least one node and one edge.
186
+ 3. **STYLE.md** (project root) — Copy from `~/.claude/skills/ftm-executor/references/STYLE-TEMPLATE.md` into the project root.
187
+ 4. **DEBUG.md** (project root) — Create with a header:
186
188
  ```markdown
187
189
  # Debug Log
188
190
 
189
191
  Failed approaches and their outcomes. Codex and Claude append here — never retry what's already logged.
190
192
  ```
191
193
 
192
- This bootstrap runs once at the start of execution. If the files already exist, skip this phase entirely.
194
+ **Phase 1.5 Gate:** After creating any missing files, verify all 4 exist:
195
+ ```bash
196
+ for f in INTENT.md ARCHITECTURE.mmd STYLE.md DEBUG.md; do
197
+ [ -f "$f" ] || echo "MISSING: $f"
198
+ done
199
+ ```
200
+ If any file is still missing after the bootstrap attempt, STOP and report:
201
+ ```
202
+ Documentation bootstrap failed — missing: [list]
203
+ Cannot proceed without documentation layer. Fix manually or re-run.
204
+ ```
205
+ Do NOT proceed to Phase 2 with missing documentation files.
193
206
 
194
207
  ---
195
208
 
package/ftm-verify.yml ADDED
@@ -0,0 +1,2 @@
1
+ name: ftm-verify
2
+ description: Comprehensive post-execution verification and auto-remediation engine using dual-model adversarial analysis. Replaces ftm-retro. After ftm-executor completes a plan, this skill runs two independent verification passes in parallel — Codex (OpenAI) and Gemini (Google) — each reading the entire codebase to check plan fulfillment, documentation fidelity, build health, test quality, and wiring integrity. Falls back to Claude subagents if either CLI is unavailable. Reconciles findings from both models, auto-remediates with parallel fix agents, and reports what was found, disagreed on, and fixed. Use when user says "verify", "is the plan done", "check everything", "verify plan", "ftm-verify", "did we miss anything", "is it complete", "validate the build", "check the plan", "verify execution", "post-execution check", or after any ftm-executor run completes. Also triggers on "retro", "retrospective", "how did that go", "execution review" since this skill supersedes ftm-retro. Even if the user just says "are we good?" after a plan execution — this is the skill.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "feed-the-machine",
3
- "version": "1.4.1",
3
+ "version": "1.5.0",
4
4
  "description": "A unified intelligence layer for Claude Code — 22 skills with OODA-based reasoning, persistent memory, multi-model deliberation, and optional operator cockpit inbox",
5
5
  "license": "MIT",
6
6
  "author": "kkudumu",